| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, "walther(at)technowledgy(dot)de" <walther(at)technowledgy(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fixing CREATEROLE |
| Date: | 2025-05-05 15:23:05 |
| Message-ID: | CAKFQuwa9tvUNs6RtnmpY1uDRaBOSBMDWkbdPPUR+OqeWrgP6TQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, May 5, 2025, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, May 1, 2025 at 2:22 PM Robert Haas <robertmhaas(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-05-05 15:26:36 | Re: RFC: Command Restrictions by INI file with Audit Logging (DROP/TRUNCATE/DELETE) |
| Previous Message | Robert Haas | 2025-05-05 15:07:01 | Re: ZStandard (with dictionaries) compression support for TOAST compression |