summaryrefslogtreecommitdiff
path: root/doc/src/sgml/protocol.sgml
diff options
context:
space:
mode:
authorNeil Conway <neilc@samurai.com>2004-11-15 06:32:15 +0000
committerNeil Conway <neilc@samurai.com>2004-11-15 06:32:15 +0000
commitec7a6bd9a23486d4eb0351de4a0c6dab5028f1ea (patch)
treeeec49035b0f2a5b12c5d0f6fb3ec98a4dd6b85f1 /doc/src/sgml/protocol.sgml
parentdb1531f6d8091c9f8dcfdeadddc3666d4b838da5 (diff)
downloadpostgresql-ec7a6bd9a23486d4eb0351de4a0c6dab5028f1ea.tar.gz
Replace "--" and "---" with "&mdash;" as appropriate, for better-looking
output.
Diffstat (limited to 'doc/src/sgml/protocol.sgml')
-rw-r--r--doc/src/sgml/protocol.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 41d4997023..15e03c3d36 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/protocol.sgml,v 1.54 2004/09/23 23:35:07 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/protocol.sgml,v 1.55 2004/11/15 06:32:14 neilc Exp $ -->
<chapter id="protocol">
<title>Frontend/Backend Protocol</title>
@@ -775,7 +775,7 @@
ErrorResponse, then reads and discards messages until a Sync is reached,
then issues ReadyForQuery and returns to normal message processing.
(But note that no skipping occurs if an error is detected
- <emphasis>while</> processing Sync --- this ensures that there is one
+ <emphasis>while</> processing Sync &mdash; this ensures that there is one
and only one ReadyForQuery sent for each Sync.)
</para>
@@ -1034,7 +1034,7 @@
value changes for any of the parameters the backend believes the
frontend should know about. Most commonly this occurs in response
to a <command>SET</> SQL command executed by the frontend, and
- this case is effectively synchronous --- but it is also possible
+ this case is effectively synchronous &mdash; but it is also possible
for parameter status changes to occur because the administrator
changed a configuration file and then sent the
<systemitem>SIGHUP</systemitem> signal to the postmaster. Also,
@@ -1119,7 +1119,7 @@
</para>
<Para>
- The cancellation signal may or may not have any effect --- for
+ The cancellation signal may or may not have any effect &mdash; for
example, if it arrives after the backend has finished processing
the query, then it will have no effect. If the cancellation is
effective, it results in the current command being terminated