Improve pg_dump/pg_restore --create --if-exists logic. Teach it not to complain if the dropStmt attached to an archive entry is actually spelled CREATE OR REPLACE VIEW, since that will happen due to an upcoming bug fix. Also, if it doesn't recognize a dropStmt, have it print a WARNING and then emit the dropStmt unmodified. That seems like a much saner behavior than Assert'ing or dumping core due to a null-pointer dereference, which is what would happen before :-(.
Back-patch to 9.4 where this option was introduced. Discussion: <[email protected]> Branch ------ REL9_6_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/0eaa5118ae457ff9873a796e08adaea1bb8172f9 Modified Files -------------- src/bin/pg_dump/pg_backup_archiver.c | 48 ++++++++++++++++++++++++------------ 1 file changed, 32 insertions(+), 16 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
