From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: -f <output file> option for pg_dumpall |
Date: | 2007-01-05 20:05:26 |
Message-ID: | 459EAF86.9030606@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Pflug wrote:
> 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).
>>
>> As far as I can see, adding a -f option to pg_dumpall should be straight
>> forward, the only issue being that we'd need to pass pg_dump an
>> additional (undocumented?) option to tell it to append to the output
>> file instead of writing it as normal.
>>
>> Any thoughts or better ideas?
>>
> Use pgAdmin's "create script" funcion on the server.
We said long ago we weren't going to replicate pg_dump functionality in
pgAdmin - a brief discussion on the pgadmin-hackers list earlier
indicates that people still feel the same way, and that time would be
better spend fixing pg_dump/pg_dumpall.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2007-01-05 20:33:36 | Re: InitPostgres and flatfiles question |
Previous Message | Dave Page | 2007-01-05 20:03:33 | Re: -f <output file> option for pg_dumpall |