pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: andy.ye@gtssz.net
Subject: BUG #16197: pg_advisory_xact_lock error
Date: Wed, 08 Jan 2020 10:38:43 +0000
Message-ID: <16197-95f237f0ed016e22@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16197
Logged by:          andy ye
Email address:      andy.ye@gtssz.net
PostgreSQL version: 9.5.12
Operating system:   ubuntu 16.04
Description:        

error log:
2020-01-07 09:45:21 UTC:172.21.1.126(41882):daladmin@mobime-pre:[21636]:LOG:
 statement: BEGIN
2020-01-07 09:45:21 UTC:172.21.1.126(41882):daladmin@mobime-pre:[21636]:LOG:
 statement: SELECT pg_advisory_xact_lock(10006, 498408);
2020-01-07 15:43:14 UTC:172.21.1.126(41882):daladmin@mobime-pre:[21636]:LOG:
 duration: 21472423.193 ms

Hello:
I found that the official documentation seems to introduce very little about
pg_advisory_xact_lock. When I check the postgresql log, I find that it can't
acquire the lock for a long time. Does this mean that the last lock was not
released or not released completely? At present I may need some help:
1. View the SQL that exists in the database pg_advisory_xact_lock and the
SQL that was manually released
2. Corresponds to the fact that I have not obtained the lock for a long
time. Can I set the lock lifetime and automatically release it for a long
time without release, that is, if the lock has not been released for a long
time last time, it will not affect the acquisition of the next lock. What
should I do? Do, since the official documentation is less, I need your
help
Sincere thanks
Dear's Andy



view thread (2+ messages)  latest in thread

Message-ID: <16197-95f237f0ed016e22@postgresql.org>
Permalink:  ../16197-95f237f0ed016e22@postgresql.org/
Also on:    postgresql.org/message-id/16197-95f237f0ed016e22@postgresql.org

 · 

reply

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 #16197: pg_advisory_xact_lock error
  In-Reply-To: <16197-95f237f0ed016e22@postgresql.org>
  References: <16197-95f237f0ed016e22@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