Re: restore whoes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Simone Tellini <tellini(at)areabusiness(dot)it>, pgsql-admin(at)postgresql(dot)org
Subject: Re: restore whoes
Date: 2002-02-11 16:02:51
Message-ID: 7010.1013443371@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I think we can live with it _if_ we report a proper error message and
> suggest a solution.

Looking for a way to report an error message misses the point entirely,
IMHO (even if it weren't a horrid kluge). I don't want to report an
error message; I want to read the file successfully. If the file in
question is your dump from an already-erased previous version, being
told that you messed it up is no help.

Adding options to the COPY command is no help either, because the COPY
may be embedded in a multi-gigabyte dump file that you can't edit
conveniently. (And what of pg_restore, or other applications that
generate COPY commands?) My approach of using a GUC variable is better
because it can be set from outside the dump script --- in
postgresql.conf, if necessary.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Oliver Elphick 2002-02-11 16:43:34 Re: Re-nameing a database?
Previous Message Naomi Walker 2002-02-11 15:56:07 Re: user to database restriction?