From: Bruno Wolff III <bruno@wolff.to>
To: Mark M. Huber <MHuber@vmdirect.com>
Cc: Naomi Walker <nwalker@eldocomp.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: backup and recovery
Date: Fri, 26 Mar 2004 14:29:39 -0600
Message-ID: <20040326202939.GC20194@wolff.to> (raw)
In-Reply-To: <C82819B1AE6E934A91FE8481153EB422A9E38A@mail.co.vmdirect.com>
References: <C82819B1AE6E934A91FE8481153EB422A9E38A@mail.co.vmdirect.com>
On Mon, Mar 22, 2004 at 09:13:06 -0800,
"Mark M. Huber" <MHuber@vmdirect.com> wrote:
> That sounds like a brilliant idea, who do we say it to make it so?
It might be better to make this part of pg_restore, rather than pg_dump.
>
> Mark H
>
> -----Original Message-----
> From: Naomi Walker [mailto:nwalker@eldocomp.com]
> Sent: Monday, March 22, 2004 8:19 AM
> To: Mark M. Huber
> Cc: Naomi Walker; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] backup and recovery
>
>
> That brings up a good point. It would be extremely helpful to add two
> parameters to pg_dump. One, to add how many rows to insert before a
> commit, and two, to live through X number of errors before dying (and
> putting the "bad" rows in a file).
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bruno@wolff.to, MHuber@vmdirect.com, nwalker@eldocomp.com
Subject: Re: backup and recovery
In-Reply-To: <20040326202939.GC20194@wolff.to>
References: <C82819B1AE6E934A91FE8481153EB422A9E38A@mail.co.vmdirect.com> <20040326202939.GC20194@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox