From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: REFERENCES privilege should not be symmetric (was Re: [GENERAL] Postgres Permissions Article) |
Date: | 2017-03-31 17:40:00 |
Message-ID: | 10730.1490982000@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Mar 31, 2017 at 11:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The argument for not back-patching a bug fix usually boils down to
>> fear of breaking existing applications, but it's hard to see how
>> removal of a permission check could break a working application ---
>> especially when the permission check is as hard to trigger as this one.
>> How many table owners ever revoke their own REFERENCES permission?
> Sure, but that argument cuts both ways. If nobody ever does that, who
> will be helped by back-patching this?
> I certainly agree that back-patching this change is pretty low risk.
> I just don't think it has any real benefits.
I think the benefit is reduction of user confusion. Admittedly, since
Paul is the first person I can remember ever having complained about it,
maybe nobody else is confused.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-03-31 17:56:30 | Re: REFERENCES privilege should not be symmetric (was Re: [GENERAL] Postgres Permissions Article) |
Previous Message | Tom Lane | 2017-03-31 17:29:24 | Re: Unexpected interval comparison |
From | Date | Subject | |
---|---|---|---|
Next Message | Anastasia Lubennikova | 2017-03-31 17:40:59 | Re: WIP: Covering + unique indexes. |
Previous Message | Tomas Vondra | 2017-03-31 17:35:55 | Re: PATCH: pageinspect / add page_checksum and bt_page_items(bytea) |