Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist
Date
Msg-id CAFj8pRBihcCEK-bcQEgCqLdLjQQ+J5PUyeZTekXHi_hoaEkoBw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-bugs
2013/2/16 Tom Lane <tgl@sss.pgh.pa.us>:
> Bruce Momjian <bruce@momjian.us> writes:
>> On Fri, Feb 15, 2013 at 04:06:12PM -0600, Dave Rolsky wrote:
>>> Fair enough. It should probably an option to add "if exists", at
>>> least. I can't imagine I'm the only using this tool to ship database
>>> updates around to different machines, some of which may not have new
>>> tables. I'd really like to be able to know when the restore fails
>>> versus when it succeeds but is noisy.
>
>> All I can say is I don't remember anyone asking for this in the past.
>
> I think it has come up before.  I wouldn't object to a pg_dump option to
> add IF EXISTS to all the drop commands (though changing the default
> behavior would be more controversial).  Don't intend to spend my own
> time on it though ...

we use this feature more than one year.

I'll send patch at Monday

Regards

Pavel Stehule



>
>                         regards, tom lane
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist
Next
From: Christian Hammers
Date:
Subject: postmaster --help does not show --config-file