Message-ID: <da68e78ba167e84fc7e58c74ac5ae64d.squirrel@webmail.tdpe.co.uk>
Date: Wed, 11 Feb 2015 10:32:13 -0000
Subject: Advisory locks
From: "Tom Paynter" <tompaynter@tdpe.co.uk>
To: pgsql-sql@postgresql.org
User-Agent: SquirrelMail/1.5.2 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Hello All,

I have a quick question about advisory locks, that I have not been able to
figure out from the documentation.


Say I have two tables:
CREATE TABLE table_a
(
table_a_id        serial primary key,
some more rows....
);

CREATE TABLE table_b
(
table_b_id        serial primary key,
some more rows....
);


And I execute the following lines (from separate sessions):
SELECT pg_advisory_lock(table_a_id) FROM table_a WHERE table_a_id=3D5;
SELECT pg_advisory_lock(table_b_id) FROM table_b WHERE table_b_id=3D5;


Will this try to acquire the same lock?
Or is the id tied to the table somehow?


Thanks for your time.
Tom


--=20
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql