Re: fixing CREATEROLE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, walther(at)technowledgy(dot)de, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fixing CREATEROLE
Date: 2025-05-07 17:16:48
Message-ID: 20839.1746638208@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, May 5, 2025 at 8:35 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> So it seems like the only real fix is to do as Tom proposes:
>> # But don't we need to add
>> # createrole_self_grant to the set of GUCs that pg_dump[all]
>> # resets in the emitted SQL?

> Tom, are you hoping that I'm going to produce a patch for this, or are
> you planning to produce one?

I wasn't planning to write the patch, no. I don't think there's any
great urgency about it, now that we've missed the deadline for the
May releases. If it gets done by August, it's fine.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-05-07 17:17:01 [PATCH] Fix missing comma in Requires.private with a Make macro
Previous Message Robert Haas 2025-05-07 17:12:59 Re: fixing CREATEROLE