From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tsirkin Evgeny <tsurkin@mail.jct.ac.il>
Cc: Naomi Walker <nwalker@eldocomp.com>
Cc: Mark M. Huber <MHuber@VMdirect.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: [Retrieved]RE: backup and recovery
Date: Wed, 24 Mar 2004 17:54:34 -0500
Message-ID: <2347.1080168874@sss.pgh.pa.us> (raw)
In-Reply-To: <200403241815.i2OIFJS02678@candle.pha.pa.us>
References: <200403241815.i2OIFJS02678@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Added to TODO:
> * Have pg_dump use multi-statement transactions for INSERT dumps
> For simple performance reasons, it would be good. I am not sure about
> allowing errors to continue loading. Anyone else?
Of course, anyone who actually cares about reload speed shouldn't be
using INSERT-style dumps anyway ... I'm not sure why we should expend
effort on that rather than just telling people to use the COPY mode.
regards, tom lane
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: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, tsurkin@mail.jct.ac.il, nwalker@eldocomp.com, MHuber@VMdirect.com
Subject: Re: [Retrieved]RE: backup and recovery
In-Reply-To: <2347.1080168874@sss.pgh.pa.us>
References: <200403241815.i2OIFJS02678@candle.pha.pa.us> <2347.1080168874@sss.pgh.pa.us>
* 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