BUG #16194: use postgresql's pg_advisory_xact_lock error

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: andy(dot)ye(at)gtssz(dot)net
Subject: BUG #16194: use postgresql's pg_advisory_xact_lock error
Date: 2020-01-07 09:33:26
Message-ID: 16194-8f7bff6e93dbe84c@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16194
Logged by: andy ye
Email address: andy(dot)ye(at)gtssz(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2020-01-07 09:42:28 Re: Unable to fork: Resource Unavailable
Previous Message andy ye 2020-01-07 09:22:16 About postgresql pg_advisory_xact_lock use!!!!