Daniel Rinehart writes:
> Our callout use of NOTIFY within a TRIGGER may be tangential to the root
> cause. What we wanted to call out is that neither the NOTIFY page or the
> https://www.postgresql.org/docs/16/explicit-locking.html page mention that
> NOTIFY uses an AccessExclusiveLock.
Like Lau
Our callout use of NOTIFY within a TRIGGER may be tangential to the root
cause. What we wanted to call out is that neither the NOTIFY page or the
https://www.postgresql.org/docs/16/explicit-locking.html page mention that
NOTIFY uses an AccessExclusiveLock.
-- Daniel R. [http://danielr.neophi.com/
On Wed, 2023-11-15 at 17:38 +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-notify.html
> Description:
>
> It would be good to add to the notes section that use of NOTIFY especially
> within
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-notify.html
Description:
It would be good to add to the notes section that use of NOTIFY especially
within a TRIGGER requires an AccessExclusiveLock which may cause performance
issues.
