Re: document the dangers of granting TRIGGER or REFERENCES

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "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:05:26
Message-ID: CAKAnmm+6JfyA+ARkzaEaVcewy4MFh5eUC_m_yMeJWN1+EzY0gg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 14, 2026 at 9:54 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> If you don't like that language, feel free to suggest alternatives.
>

+1, good idea.

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. I could see some pushback for triggers, but still
a +1 on that as well, as it should not break anything sane, and can easily
be worked around.

--
Cheers,
Greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-07-14 15:20:51 Re: Make pg_prewarm, autoprewarm yield for waiting DDL
Previous Message Robert Haas 2026-07-14 15:02:56 Re: LockHasWaiters() crashes on fast-path locks