|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.176 2006/12/05 17:40:55 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.177 2006/12/06 15:40:11 momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -87,9 +87,10 @@ PostgreSQL documentation |
87 | 87 | it contains no <application>psql</application> specific features), |
88 | 88 | or a single backslash command. Thus you cannot mix |
89 | 89 | <acronym>SQL</acronym> and <application>psql</application> |
90 | | - meta-commands. To achieve that, you could pipe the string into |
91 | | - <application>psql</application>, like this: <literal>echo -e |
92 | | - "\\x\nSELECT * FROM foo;" | psql</literal>. |
| 90 | + meta-commands with this option. To achieve that, you could |
| 91 | + pipe the string into <application>psql</application>, like |
| 92 | + this: <literal>echo "\x \\ SELECT * FROM foo;" | psql</literal>. |
| 93 | + (<literal>\\</> is the separator meta-command.) |
93 | 94 | </para> |
94 | 95 | <para> |
95 | 96 | If the command string contains multiple SQL commands, they are |
|