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
4fe24467
Commit
4fe24467
authored
26 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Add note explaining that NoticeResponse messages can
arrive even while idle.
parent
22da903a
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/protocol.sgml
+14
-4
14 additions, 4 deletions
doc/src/sgml/protocol.sgml
with
14 additions
and
4 deletions
doc/src/sgml/protocol.sgml
+
14
−
4
View file @
4fe24467
...
@@ -4,7 +4,7 @@
...
@@ -4,7 +4,7 @@
<FirstName>Phil</FirstName>
<FirstName>Phil</FirstName>
<Surname>Thompson</Surname>
<Surname>Thompson</Surname>
</Author>
</Author>
<Date>1998-0
7-13
</Date>
<Date>1998-0
8-08
</Date>
</DocInfo>
</DocInfo>
<Title>Frontend/Backend Protocol</Title>
<Title>Frontend/Backend Protocol</Title>
...
@@ -389,9 +389,19 @@ The possible response messages from the backend are:
...
@@ -389,9 +389,19 @@ The possible response messages from the backend are:
<Para>
<Para>
A frontend must be prepared to accept ErrorResponse and NoticeResponse
A frontend must be prepared to accept ErrorResponse and NoticeResponse
messages whenever it is expecting any other type of message. Also,
messages whenever it is expecting any other type of message.
if it issues any listen(l) commands then it must be prepared to accept
NotificationResponse messages at any time; see below.
<Para>
Actually, it is possible for NoticeResponse to arrive even when the frontend
is not expecting any kind of message, that is, the backend is nominally idle.
(In particular, the backend can be commanded to terminate by its postmaster.
In that case it will send a NoticeResponse before closing the connection.)
It is recommended that the frontend check for such asynchronous notices just
before issuing any new command.
<Para>
Also, if the frontend issues any listen(l) commands then it must be prepared
to accept NotificationResponse messages at any time; see below.
<Sect2>
<Sect2>
...
...
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