On Mon, Jan 15, 2007 at 10:13:16AM -0500, Andrew Dunstan wrote:
Neil Conway wrote:
On Thu, 2007-01-11 at 14:36 -0500, Neil Conway wrote:
I don't think they need to be integrated any time soon, but if we were
to design pg_dump and pg_dumpall from scratch, it seems more logical to
use a
elein wrote:
On Mon, Jan 15, 2007 at 10:13:16AM -0500, Andrew Dunstan wrote:
Neil Conway wrote:
On Thu, 2007-01-11 at 14:36 -0500, Neil Conway wrote:
I don't think they need to be integrated any time soon, but if we were
to design pg_dump and pg_dumpall from scratch, it seems more logical
Neil Conway wrote:
On Thu, 2007-01-11 at 14:36 -0500, Neil Conway wrote:
I don't think they need to be integrated any time soon, but if we were
to design pg_dump and pg_dumpall from scratch, it seems more logical to
use a single program
On thinking about this some more, it might be
On Thu, 2007-01-11 at 14:36 -0500, Neil Conway wrote:
I don't think they need to be integrated any time soon, but if we were
to design pg_dump and pg_dumpall from scratch, it seems more logical to
use a single program
On thinking about this some more, it might be useful to factor much of
Possibly, to merge the two programs. I'm intending to put some time into
the append and seperating globals items, but I don't think I have the
time to merge the apps given Tom's concerns and some further investigation.
Regards, Dave.
Bruce Momjian wrote:
Is there a TODO here?
Dave Page wrote:
Possibly, to merge the two programs. I'm intending to put some time into
the append and seperating globals items, but I don't think I have the
time to merge the apps given Tom's concerns and some further investigation.
Yes, I was just wondering if an append mode for Win32
On Fri, 2007-01-05 at 17:52 -0500, Tom Lane wrote:
I think this will be an exercise in time-wasting, and very possibly
destabilize *both* tools. pg_dump has never been designed to reconnect
to a different database; for instance there isn't any code for resetting
all the internal state that it
Andreas Pflug wrote:
Not much function to re-create here, single
exception is extracting cluster wide data, the -g option, that's why I
mentioned scripting. But apparently this didn't get into pgadmin svn any
more, so I need to retract this proposal.
Eh? Your SCRIPT code is still there - or
Dave Page wrote:
Andreas Pflug wrote:
Not much function to re-create here, single
exception is extracting cluster wide data, the -g option, that's why I
mentioned scripting. But apparently this didn't get into pgadmin svn any
more, so I need to retract this proposal.
Eh? Your
Dave Page wrote:
I don't object to it in principle, but I think a bit more thought is
needed as to what's the goal. A stupid append option would be enough
for pg_dumpall's current capabilities (ie, text output only) --- but is
it reasonable to consider generalizing -Fc and -Ft modes to deal
On Fri, Jan 05, 2007 at 08:05:26PM +, Dave Page wrote:
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
Jim C. Nasby wrote:
It might make sense to provide a programmatic interface to pg_dump to
provide tools like pgAdmin more flexibility.
Are you talking about pg_dump in a lib? Certainly a good idea, because
it allows better integration (e.g. progress bar).
But it certainly doesn't make sense
--- Original Message ---
From: Tom Lane [EMAIL PROTECTED]
To: Dave Page [EMAIL PROTECTED]
Sent: 1/5/07, 10:48:17 PM
Subject: Re: [HACKERS] -f output file option for pg_dumpall
Wouldn't it be easier/better to re-point stdout at the -f file, and not
touch pg_dump at all?
First
--- Original Message ---
From: Tom Lane [EMAIL PROTECTED]
To: Dave Page [EMAIL PROTECTED]
Sent: 1/5/07, 10:52:37 PM
Subject: Re: [HACKERS] -f output file option for pg_dumpall
I think this will be an exercise in time-wasting, and very possibly
destabilize *both* tools. pg_dump
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
Dave Page [EMAIL PROTECTED] writes:
From: Tom Lane [EMAIL PROTECTED]
I think forking a separate
pg_dump for each database is a perfectly fine arrangement, and should be
left alone.
Hmm, would you be happy with my original proposal to add an append option to
pg_dump?
I don't object to it
Peter Eisentraut 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
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
From: Tom Lane [EMAIL PROTECTED]
I think forking a separate
pg_dump for each database is a perfectly fine arrangement, and should be
left alone.
Hmm, would you be happy with my original proposal to add an append option to
pg_dump?
I
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
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?
Yeah :) Getting
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
On Friday 05 January 2007 09:40, Andrew Dunstan 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
On Fri, Jan 05, 2007 at 12:40:20PM -0500, Andrew Dunstan 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
David Fetter wrote:
This seems a bit like piecemeal reform. Here are some things I'd like to
see that affect this area:
. merge pg_dump and pg_dumpall (e.g. add a flag to pg_dump that says do
the lot)
. multi-db non-text dumps
And while we're about it, can we teach pg_restore to handle text
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
Dave Page [EMAIL PROTECTED] writes:
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.
Wouldn't it
Dave Page [EMAIL PROTECTED] writes:
Hmm, well I have no interest in the latter at present, but assuming the
powers that be will allow me some time to do so, I will look at merging
pg_dump and pg_dumpall as that seems to be the way people want to go.
I think this will be an exercise in
Tom Lane schrieb:
Dave Page [EMAIL PROTECTED] writes:
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
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
29 matches
Mail list logo
