From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: andy.ye@gtssz.net
Subject: BUG #16194: use postgresql's pg_advisory_xact_lock error
Date: Tue, 07 Jan 2020 09:33:26 +0000
Message-ID: <16194-8f7bff6e93dbe84c@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16194
Logged by: andy ye
Email address: andy.ye@gtssz.net
PostgreSQL version: 9.5.11
Operating system: ubuntu 16.04
Description:
When I use postgresql's pg_advisory_xact_lock for transaction security,
especially RPC services, I often see that the lock is not released, causing
the service to block for a long time. The blocking time is about 15 minutes.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, andy.ye@gtssz.net
Subject: Re: BUG #16194: use postgresql's pg_advisory_xact_lock error
In-Reply-To: <16194-8f7bff6e93dbe84c@postgresql.org>
References: <16194-8f7bff6e93dbe84c@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox