Re: BUG #3760: Comment on restore database

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Malcus Imhof <malcus(at)terra(dot)com(dot)br>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3760: Comment on restore database
Date: 2007-11-20 08:24:50
Message-ID: 1195547090.4217.164.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 2007-11-19 at 18:38 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Reason to do this now: Perf Tips have been changed for 8.3 to recommend
> > using --single-transaction when restoring pg_dumps, because of fast COPY
> > enhancement. Allowing this to cause an error will prevent the whole dump
> > from restoring.
>
> If it were indeed an error condition, this argument might have some
> merit. Since it is not, I don't have a lot of sympathy for a hasty
> last-minute change.

Well, if its not an ERROR condition, no problem. I interpreted failure
to mean ERROR, which luckily it isn't.

The failure of the COMMENT isn't any reason for a last-minute change, so
request withdrawn.

--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message migo 2007-11-20 10:12:49 BUG #3763: crash after create table with primary key defined
Previous Message Cstdenis 2007-11-20 07:57:27 BUG #3762: Inherited serials change on dump/restore