Hello 2013/2/21 Josh Kupershmidt <schmi...@gmail.com>: > On Tue, Feb 19, 2013 at 6:00 AM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: >> 2013/2/16 Pavel Stehule <pavel.steh...@gmail.com>: >>> 2013/2/16 Tom Lane <t...@sss.pgh.pa.us>: >>>> 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 ... > > FYI, it was proposed here: > http://www.postgresql.org/message-id/507ad08c.5020...@dalibo.com > >> here is patch, that we use about one year - originally for 9.1 - I did >> port to 9.3 > > dropdb and dropuser both support a similar option named --if-exists. I > suggest --if-exists instead of --conditional-drops for consistency. > I've only glanced at the patch, but if it makes no sense to use > --conditional-drops (or --if-exists, whatever it ends up being called) > without --clean, then attempting to do so should raise an error.
so * --conditional-drops replaced by --if-exists * -- additional check, available only with -c option * fix bug with dump custom functions Regards Pavel > > Josh
conditional-drops.patch
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
