Re: document the dangers of granting TRIGGER or REFERENCES

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: document the dangers of granting TRIGGER or REFERENCES
Date: 2026-07-14 15:54:07
Message-ID: 3337796.1784044447@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Sabino Mullane <htamfids(at)gmail(dot)com> writes:
> On Tue, Jul 14, 2026 at 9:54 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> IMHO, apart from patching the documentation, the other thing we might
>> want to consider doing is removing one or both of these privileges
>> entirely, and making them part of table ownership.

> Big +1 for references.

REFERENCES is required by SQL spec, no?

(hmm, actually, TRIGGER is too ...)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-07-14 15:56:49 Re: document the dangers of granting TRIGGER or REFERENCES
Previous Message ZizhuanLiu X-MAN 2026-07-14 15:49:34 Re: Reject unsupported COPY FROM targets before analyzing WHERE clause