Re:The pitfall of using PostgreSQL advisory locks with Go's ...
by AlfeG on Sunday September 01, 2019 @01:41AM
(#20850663)
For transactions You should use different advisory lock tied to transaction: pg_advisory_xact_lock. This should solve problem even for sessions reuse and connection pooling
[ Parent
| on HN ]
There are no comments on this comment yet.