Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-ID: <20150211104038.5402756.43145.2247@gmail.com>
Date: Wed, 11 Feb 2015 11:40:38 +0100
Subject: Re: Advisory locks
From: daku.sandor@gmail.com
In-Reply-To: <da68e78ba167e84fc7e58c74ac5ae64d.squirrel@webmail.tdpe.co.uk>
References: <da68e78ba167e84fc7e58c74ac5ae64d.squirrel@webmail.tdpe.co.uk>
To: Tom Paynter <tompaynter@tdpe.co.uk>, pgsql-sql@postgresql.org
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

The parameter of the pg_advisory_lock is a simple bigint and of course it i=
s completely unaware of the source of the value.

Regards,
S=E1ndor Daku

=A0 Original Message =A0
From: Tom Paynter
Sent: 2015. febru=E1r 11., szerda 11:33
To: pgsql-sql@postgresql.org
Subject: [SQL] Advisory locks

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


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