aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-11-17 14:59:23 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-11-17 14:59:23 -0500
commita7864037d8b7fd172d870782a8024d3f96b0b17b (patch)
treef2c103a9eb25a6d9b05cc25da8f6cdbe4f9ac1d6 /src/backend/access/transam/commit_ts.c
parentc0db1ec2600a898ac75d14057e01fb716059a2f5 (diff)
downloadpostgresql-a7864037d8b7fd172d870782a8024d3f96b0b17b.tar.gz
postgresql-a7864037d8b7fd172d870782a8024d3f96b0b17b.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/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions