Re: fixing CREATEROLE - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: fixing CREATEROLE
Date
Msg-id CAKFQuwa9tvUNs6RtnmpY1uDRaBOSBMDWkbdPPUR+OqeWrgP6TQ@mail.gmail.com
Whole thread Raw
In response to Re: fixing CREATEROLE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


On Monday, May 5, 2025, Robert Haas <robertmhaas@gmail.com> wrote:
On Thu, May 1, 2025 at 2:22 PM Robert Haas <robertmhaas@gmail.com> wrote:
> > The other approach would be to do what we do for the role options and just specify everything explicitly in the dump.  The GUC is only a default specifier so let's not leave room for defaults in the dump file.
>
> +1 for considering that option, although I am not sure which way is better.

Actually, on further reflection, this doesn't work, right?

Doh.  I was thinking this was controlling admin/inherit/set defaults but you are correct this controls whether additional commands are emitted automatically instead of having to make it so manually.

David J.
 

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ZStandard (with dictionaries) compression support for TOAST compression
Next
From: "David G. Johnston"
Date:
Subject: Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE)