diff options
| -rw-r--r-- | doc/src/sgml/ref/psql-ref.sgml | 20 |
1 files changed, 17 insertions, 3 deletions
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 49ad740a4c3..803fc503a64 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -88,8 +88,8 @@ PostgreSQL documentation or a single backslash command. Thus you cannot mix <acronym>SQL</acronym> and <application>psql</application> meta-commands with this option. To achieve that, you could - pipe the string into <application>psql</application>, like - this: <literal>echo '\x \\ SELECT * FROM foo;' | psql</literal>. + pipe the string into <application>psql</application>, for example: + <literal>echo '\x \\ SELECT * FROM foo;' | psql</literal>. (<literal>\\</> is the separator meta-command.) </para> <para> @@ -98,7 +98,21 @@ PostgreSQL documentation <command>BEGIN</>/<command>COMMIT</> commands included in the string to divide it into multiple transactions. This is different from the behavior when the same string is fed to - <application>psql</application>'s standard input. + <application>psql</application>'s standard input. Also, only + the result of the last SQL command is returned. + </para> + <para> + Because of these legacy behaviors, putting more than one command in + the <option>-c</option> string often has unexpected results. It's + better to feed multiple commands to <application>psql</application>'s + standard input, either using <application>echo</application> as + illustrated above, or via a shell here-document, for example: +<programlisting> +psql <<EOF +\x +SELECT * FROM foo; +EOF +</programlisting> </para> </listitem> </varlistentry> |