Re: Feature bug dumpall CREATE ROLE postgres

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Wilson <jim(at)wreath(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Feature bug dumpall CREATE ROLE postgres
Date: 2024-02-28 22:47:22
Message-ID: 4f7760bd-243b-6eb1-4c4d-de07200012f9@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 2024-02-28 We 17:36, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.
>
>

This is only for pg_dumpall. pg_restore shouldn't care.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-02-28 22:53:12 Re: Feature bug dumpall CREATE ROLE postgres
Previous Message Tom Lane 2024-02-28 22:36:13 Re: Feature bug dumpall CREATE ROLE postgres