Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
f1fef841
Commit
f1fef841
authored
26 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Grammar, my boy, grammar :-(
parent
af5d6b4e
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/ref/notify.sgml
+6
-6
6 additions, 6 deletions
doc/src/sgml/ref/notify.sgml
with
6 additions
and
6 deletions
doc/src/sgml/ref/notify.sgml
+
6
−
6
View file @
f1fef841
...
...
@@ -147,16 +147,16 @@ after the transaction is completed (either committed or aborted). Again, the
reasoning is that if a notify were delivered within a transaction that was
later aborted, one would want the notification to be undone somehow --- but
the backend cannot "take back" a notify once it has sent it to the frontend.
So notify events are delivered
only
between transactions. The upshot of this
So notify events are
only
delivered between transactions. The upshot of this
is that applications using <command>NOTIFY</command> for real-time signaling
should try to keep their transactions short.
<para>
<command>NOTIFY</command> behaves
rather
like Unix signals in one important
respect: if the same
notify
name is signaled multiple times in quick
<command>NOTIFY</command> behaves like Unix signals in one important
respect: if the same
condition
name is signaled multiple times in quick
succession, recipients may get only one notify event for several executions
of <command>NOTIFY</command>. So it is a bad idea to depend on the number
of notifies received
; i
nstead use <command>NOTIFY</command> to wake up
of notifies received
. I
nstead
,
use <command>NOTIFY</command> to wake up
applications that need to pay attention to something, and use a database
object (such as a sequence) to keep track of what happened or how many times
it happened.
...
...
@@ -201,8 +201,8 @@ table name, even if syntactically valid as a name. That is no longer required.
<para>
In <productname>Postgres</productname> releases prior to 6.4, the backend
PID delivered in a notify message
i
s always the PID of the frontend's own
backend. So it
i
s not possible to distinguish one's own notifies from other
PID delivered in a notify message
wa
s always the PID of the frontend's own
backend. So it
wa
s not possible to distinguish one's own notifies from other
clients' notifies in those earlier releases.
</REFSECT2>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment