BUG #13920: pg_try_advisory_xact_lock bigint trouble - Mailing list pgsql-bugs

From mtakvel@gmail.com
Subject BUG #13920: pg_try_advisory_xact_lock bigint trouble
Date
Msg-id 20160205132645.2661.77360@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #13920: pg_try_advisory_xact_lock bigint trouble  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      13920
Logged by:          Valeriy
Email address:      mtakvel@gmail.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.

pgsql-bugs by date:

Previous
From: jeffrey.osborn@am.sony.com
Date:
Subject: BUG #13928: Initdb.bat will not install if path has a space.
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #13936: jsonb_object() -> ERROR: unknown type of jsonb container