Skip to content

P
Postgres FD Implementation
Commit 07104991 authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Small wording tweaks 

Dmitry Igrishin
parent c6ea616f
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
doc/src/sgml/catalogs.sgml
View file @ 07104991
...@@ -8496,7 +8496,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx ...@@ -8496,7 +8496,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
<entry><type>boolean</type></entry> <entry><type>boolean</type></entry>
<entry> <entry>
<literal>true</literal> if the prepared statement was created <literal>true</literal> if the prepared statement was created
via the <command>PREPARE</command> SQL statement; via the <command>PREPARE</command> SQL command;
<literal>false</literal> if the statement was prepared via the <literal>false</literal> if the statement was prepared via the
frontend/backend protocol frontend/backend protocol
</entry> </entry>
......
src/interfaces/libpq/fe-protocol3.c
View file @ 07104991
...@@ -163,7 +163,7 @@ pqParseInput3(PGconn *conn) ...@@ -163,7 +163,7 @@ pqParseInput3(PGconn *conn)
/* /*
* Unexpected message in IDLE state; need to recover somehow. * Unexpected message in IDLE state; need to recover somehow.
* ERROR messages are displayed using the notice processor; * ERROR messages are handled using the notice processor;
* ParameterStatus is handled normally; anything else is just * ParameterStatus is handled normally; anything else is just
* dropped on the floor after displaying a suitable warning * dropped on the floor after displaying a suitable warning
* notice. (An ERROR is very possibly the backend telling us why * notice. (An ERROR is very possibly the backend telling us why
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment