Re: Should \o mean "everything?"
От | Kevin Grittner |
---|---|
Тема | Re: Should \o mean "everything?" |
Дата | |
Msg-id | 878225557.2353566.1441048682150.JavaMail.yahoo@mail.yahoo.com обсуждение исходный текст |
Ответ на | Should \o mean "everything?" (David Fetter <david@fetter.org>) |
Ответы |
Re: Should \o mean "everything?"
Re: Should \o mean "everything?" |
Список | pgsql-hackers |
David Fetter <david@fetter.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
В списке pgsql-hackers по дате отправления: