From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | justin(at)tonic(dot)ai, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17753: pg_dump --if-exists bug |
Date: | 2023-01-19 15:38:00 |
Message-ID: | 4062761.1674142680@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Thu, 19 Jan 2023 at 22:31, PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> Running pg_dump with the options "--section=pre-data --no-owner
>> --no-privileges --no-subscriptions --no-publications --clean --if-exists
>> --file=/Users/ju5tinz/Dev/pg_pass_test/pre_data.sql" prints the warning:
>> pg_dump: warning: could not find where to insert IF EXISTS in statement "--
>> *not* dropping schema, since initdb creates it
>> "
> Are you able to share the full warning message including the statement?
Noting that that string is only associated with the public schema,
I tried dumping a DB in which the public schema had been dropped
--- no dice --- and then recreated --- and then it reproduces!
Apparently, a schema that's named "public" but isn't the original
one is confusing something somewhere, but I'm not immediately
seeing where.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2023-01-19 18:02:11 | BUG #17754: Subquery IN clause returns row matches where subquery is invalid |
Previous Message | Amit Kapila | 2023-01-19 11:07:55 | Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1 |