Marcos Magueta <[email protected]> writes:
> I would be willing to at least get started with a patch for this, but
> before that, I want to assess the interest and thoughts on how to properly
> implement it.
Everyone who has looked at that has run away screaming. The
consequences for performance, complexity, deadlock potential,
etc are all horrible. There are also fun questions about
appropriate permissions. As the spec is written, it appears
that anyone with read permission on a table can block updates
on that table (by creating an assertion that attempted updates
will fail).
> FWIW, this is part of the SQL Standard: ISO/IEC 9075-2:2023, 11.47:
Yup. We are not obligated to implement everything in the
standard.
> If there's already a thread on the issue, forgive me, but I couldn't find
> it in the archives.
It's been discussed, though not recently.
regards, tom lane
