aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/array_userfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-01-19 19:32:46 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2023-01-19 19:32:50 -0500
commit74739d1d3ff6b408895a5908657ffb0648df3d70 (patch)
tree5d398de36d2fc3cf2a876e82e5f56531d9e11229 /src/backend/utils/adt/array_userfuncs.c
parent9f1ca6ce6596f1f77adc323769f2f8303ddad14f (diff)
downloadpostgresql-74739d1d3ff6b408895a5908657ffb0648df3d70.tar.gz
postgresql-74739d1d3ff6b408895a5908657ffb0648df3d70.zip
Avoid harmless warning from pg_dump --if-exists mode.
If the public schema has a non-default owner (perhaps due to dropping and recreating it) then use of pg_dump's "--if-exists" option results in a warning message: warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it" This is harmless since the dump output is the same either way, but nonetheless it's undesirable. It's the fault of commit a7a7be1f2, which created situations where a TOC entry's "defn" or "dropStmt" fields could be just comments. Although that commit fixed up the kluges in pg_backup_archiver.c that munge defn strings, it missed doing so for the one that munges dropStmts. Per bug# 17753 from Justin Zhang. Discussion: https://postgr.es/m/17753-9c8773631747ee1c@postgresql.org
Diffstat (limited to 'src/backend/utils/adt/array_userfuncs.c')
0 files changed, 0 insertions, 0 deletions