aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-11-17 14:59:19 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-11-17 14:59:19 -0500
commit0eaa5118ae457ff9873a796e08adaea1bb8172f9 (patch)
tree12711410fccddcbb25dbbdb0c158d9d74440a79d /src/test/modules/commit_ts
parentf5d89443203480e39a6a15e64f1950c3b4d3c9a2 (diff)
downloadpostgresql-0eaa5118ae457ff9873a796e08adaea1bb8172f9.tar.gz
postgresql-0eaa5118ae457ff9873a796e08adaea1bb8172f9.zip
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: <19092.1479325184@sss.pgh.pa.us>
Diffstat (limited to 'src/test/modules/commit_ts')
0 files changed, 0 insertions, 0 deletions