Re: pg_dump restore error

From: Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump restore error
Date: 2012-10-14 22:17:46
Message-ID: 507B3A0A.6060201@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 14/10/2012 18:50, Tom Lane a écrit :
> Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> writes:
>> Restoring a backup generated with pg_dump/pg_dumpall in plain text
>> format and the --clean option will report errors if the backup is loaded
>> in an other or empty database.
> This is intentional. What you propose amounts to a fundamental change
> in the semantics of --clean, and I don't think that it's really much
> of an improvement.

I'm agree that this is not an improvement, I used to work with it
because I know it's harmless error messages. The request comes from a
client that claims that replaying his backup on a new server was always
producing those errors.

I was just thinking that cleaning if exists was also harmless, but it is
probably better to have error reported in most of the cases.

Regards,

--
Gilles Darold
Administrateur de bases de données
http://dalibo.com - http://dalibo.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2012-10-14 23:06:27 Re: Potential autovacuum optimization: new tables
Previous Message Brar Piening 2012-10-14 21:34:54 Re: Visual Studio 2012 RC