| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: Mystery with REVOKE PRIVILEGE |
| Date: | 2026-01-20 23:07:13 |
| Message-ID: | 1934014.1768950433@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> On Tue, Jan 20, 2026 at 04:32:31PM -0500, Tom Lane wrote:
>> I don't think "let's make select_best_grantor even more magic"
>> is the right approach. IMO, if there is a GRANTED BY clause,
>> we should use exactly that grantor and not apply select_best_grantor
>> at all. This is, for example, certainly the behavior needed for
>> pg_dump.
> I started on something like that here:
> https://postgr.es/m/aRYLkTpazxKhnS_w%40nathan
Ah, I wonder if that discussion was lurking in my hindbrain.
I just posted a different take on how to do it in that thread,
but the behavioral change should be the same.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-01-20 23:10:49 | Re: [PATCH] Reserve protocol 3.1 explicitly in pqcomm.h |
| Previous Message | Jacob Champion | 2026-01-20 23:04:44 | [PATCH] Reserve protocol 3.1 explicitly in pqcomm.h |