From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jim Wilson <jim@wreath.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Feature bug dumpall CREATE ROLE postgres
Date: Wed, 28 Feb 2024 17:36:13 -0500
Message-ID: <2549130.1709159773@sss.pgh.pa.us> (raw)
In-Reply-To: <8663cc11-4a1c-68fa-d950-fdc863f28f4b@dunslane.net>
References: <CABboei8cKxParK=nGwjHp0i=5xdn9YtkUQAo=_vuGm-F8X46gw@mail.gmail.com>
<2149099.1709064762@sss.pgh.pa.us>
<8663cc11-4a1c-68fa-d950-fdc863f28f4b@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> What if we just skip creating the role if it's the bootstrap superuser
> in the source and has the same name as the bootstrap superuser in the
> destination, using some DO processing?
Hmm ... pg_dump has never used any DO blocks in its output, and
I'm not sure it's a great idea to start. Seems like the kind of
decision we could regret down the road, given the possible need
for pg_restore to parse the output.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, jim@wreath.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Feature bug dumpall CREATE ROLE postgres
In-Reply-To: <2549130.1709159773@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox