diff options
author | Stephen Frost <sfrost@snowman.net> | 2017-06-28 10:33:57 -0400 |
---|---|---|
committer | Stephen Frost <sfrost@snowman.net> | 2017-06-28 10:33:57 -0400 |
commit | 4500edc7e9cf771bf8960d1f3f620917871bdb6f (patch) | |
tree | 6bed94a2280ca4a7f3f5aa7672b3312366316bfa /src/backend/executor/nodeModifyTable.c | |
parent | f0256c774daa0dac96154e7ddf54197fb2b83f4d (diff) | |
download | postgresql-4500edc7e9cf771bf8960d1f3f620917871bdb6f.tar.gz postgresql-4500edc7e9cf771bf8960d1f3f620917871bdb6f.zip |
Do not require 'public' to exist for pg_dump -c
Commit 330b84d8c4 didn't contemplate the case where the public schema
has been dropped and introduced a query which fails when there is no
public schema into pg_dump (when used with -c).
Adjust the query used by pg_dump to handle the case where the public
schema doesn't exist and add tests to check that such a case no longer
fails.
Back-patch the specific fix to 9.6, as the prior commit was.
Adding tests for this case involved adding support to the pg_dump
TAP tests to work with multiple databases, which, while not a large
change, is a bit much to back-patch, so that's only done in master.
Addresses bug #14650
Discussion: https://www.postgresql.org/message-id/20170512181801.1795.47483%40wrigleys.postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions