Skip site navigation (1) Skip section navigation (2)

Re: [Retrieved]RE: backup and recovery

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il>,Naomi Walker <nwalker(at)eldocomp(dot)com>,"Mark M(dot) Huber" <MHuber(at)VMdirect(dot)com>,"pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: [Retrieved]RE: backup and recovery
Date: 2004-03-24 23:07:37
Message-ID: 200403242307.i2ON7bD26576@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.

My bigger issue is that COPY will fail on a single row failure, and
nothing will be in the table, while INSERT will not.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2004-03-24 23:41:44
Subject: Re: [Retrieved]RE: backup and recovery
Previous:From: Naomi WalkerDate: 2004-03-24 22:58:16
Subject: Re: [Retrieved]RE: backup and recovery

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group