| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | "Mark M(dot) Huber" <MHuber(at)vmdirect(dot)com> |
| Cc: | Naomi Walker <nwalker(at)eldocomp(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: backup and recovery |
| Date: | 2004-03-26 20:29:39 |
| Message-ID: | 20040326202939.GC20194@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Mar 22, 2004 at 09:13:06 -0800,
"Mark M. Huber" <MHuber(at)vmdirect(dot)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(at)eldocomp(dot)com]
> Sent: Monday, March 22, 2004 8:19 AM
> To: Mark M. Huber
> Cc: Naomi Walker; pgsql-admin(at)postgresql(dot)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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Kambhampaty | 2004-03-26 20:30:19 | Re: [Retrieved]RE: backup and recovery |
| Previous Message | Doug Quale | 2004-03-26 19:32:22 | Re: License for PostgreSQL for commercial purpose |