BUG #13920: pg_try_advisory_xact_lock bigint trouble

From: mtakvel(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13920: pg_try_advisory_xact_lock bigint trouble
Date: 2016-02-05 13:26:45
Message-ID: 20160205132645.2661.77360@wrigleys.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: 13920
Logged by: Valeriy
Email address: mtakvel(at)gmail(dot)com
PostgreSQL version: 9.5.0
Operating system: Ubuntu
Description:

Hello, I have few high load big tables. My logic calls
pg_try_advisory_xact_lock(bitint) for locking row in current table. As I see
with bigint param pg_try_advisory_xact_lock lock same ids for all my tables.
Insthead lock only row in one current table. Looks like this is bug and will
be cool if you fix it.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message jeffrey.osborn 2016-02-06 00:41:59 BUG #13928: Initdb.bat will not install if path has a space.
Previous Message mail 2016-02-05 11:35:28 BUG #13919: Cast error when table is empty.