| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Dave Page <dpage(at)postgresql(dot)org> |
| Subject: | Re: -f <output file> option for pg_dumpall |
| Date: | 2007-01-06 11:42:51 |
| Message-ID: | 200701061242.52049.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Page wrote:
> In pgAdmin we use pg_dump's -f option to write backup files. The IO
> streams are redirected to display status and errors etc. in the GUI.
>
> In order to enhance the interface to allow backup of entire clusters
> as well as role and tablespace definitions, we need to be able to get
> pg_dumpall to write it's output directly to a file in the same way,
> because we cannot redirect the child pg_dump IO streams (which also
> means we may miss errors, but I need to think about that some more).
I don't understand this. Errors are sent to stderr, and the real output
is sent to stdout, where you can capture and save it. What is the
problem?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-01-06 14:41:02 | Re: [HACKERS] wal_checksum = on (default) | off |
| Previous Message | Simon Riggs | 2007-01-06 09:46:40 | Re: Parsing ambiguity for ORDER BY ... NULLS FIRST/LAST |