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

From Tom Lane
Subject Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist
Date
Msg-id 11257.1361032501@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist  (Bruce Momjian <bruce@momjian.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
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 ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: BUG #7884: pg_upgradecluster is terribly slow
Next
From: Pavel Stehule
Date:
Subject: Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist