In this page, you mention:
The Transaction Pooling Mode for PgBouncer cannot be used with Advisory Locks
Can you expand a title further on this? PgBouncer is like a first resource when people run out of database connections, and now that it supports prepared statements people are much more inclined to continue to use it.
With the increase awareness of advisory locks and things like
GoodJob background job processing, are we increasing the risk of problems?
In the table for features for PGBouncer we can find some information: PgBouncer features
Do you think that having a more detailed explanation on the risks and what we should do to ensure to remain compatible (using session pooling, basically)
Even after reading the
Choosing A PgBouncer Pooling Mode in page 190 and when using
GoodJob, being the transaction mode, the most common, the user can easily fall in the trap of choosing the most common method to later release it’s not supported.