From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Should \o mean "everything?" |
Date: | 2015-08-31 19:18:02 |
Message-ID: | 878225557.2353566.1441048682150.JavaMail.yahoo@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> wrote:
> In a failed attempt to send the output of \pset to a pipe, I
> noticed that for reasons I find difficult to explain, not every
> output gets redirected with \o.
>
> At first blush, I'd consider this inconsistency as a bug.
>
> What have I missed?
The documentation says:
| Arranges to save future query results to the file filename or
| pipe future results to the shell command command. If no argument
| is specified, the query output is reset to the standard output.
|
| "Query results" includes all tables, command responses, and
| notices obtained from the database server, as well as output of
| various backslash commands that query the database (such as \d),
| but not error messages.
Are you seeing anything inconsistent with the documentation? If
so, what?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-08-31 19:23:23 | Re: Information of pg_stat_ssl visible to all users |
Previous Message | Alvaro Herrera | 2015-08-31 19:13:05 | Re: Anybody have icc for IA64? |