From: Mario Splivalo <mario.splivalo@mobart.hr>
To: pgsql-sql@postgresql.org
Subject: 'locking' the SELECTs based on indices...
Date: Wed, 22 Feb 2006 19:02:30 +0100
Message-ID: <1140631350.14229.8.camel@localhost.localdomain> (raw)
I have a table, like this:
CREATE TABLE bla (id int4, code_id int4, code_value varchar, CONSTRAINT
bla_pk PRIMARY KEY (id))
And, i have index on the table:
CREATE INDEX bla_idx1 ON bla(code_id)
Now, when I do this from one connection (psql shell, for instance):
[A]BEGIN TRANSACTION;
[A]SELECT * FROM bla WHERE code_id = 1 FOR UPDATE;
and then, from another psql i do:
[B]SELECT * FROM bla WHERE code_id = 1 FOR UPDATE
the second SELECT will wait untill I rollback or commit first
transaction. That is cool.
But, if I do second SELECT like this:
[C]SELECT * FROM bla WHERE code_id = 2 FOR UPDATE
I will get the rows.
If I erase the index bla_idx1, then [C] select will wait, same as [B]
select will wait. Is there a way to have this behaviour with the index
on column code_id?
Mario
--
Mario Splivalo
Mob-Art
mario.splivalo@mobart.hr
"I can do it quick, I can do it cheap, I can do it well. Pick any two."
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mario.splivalo@mobart.hr
Subject: Re: 'locking' the SELECTs based on indices...
In-Reply-To: <1140631350.14229.8.camel@localhost.localdomain>
* 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