locking bug? - Mailing list pgsql-hackers

From Max Khon
Subject locking bug?
Date
Msg-id Pine.BSF.4.21.0012162247020.45566-100000@iclub.nsu.ru
Whole thread Raw
Responses Re: locking bug?  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-hackers
hi, there!

test=> create table foo(id int primary key);
NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'foo_pkey'
for table 'foo'
CREATE
test=> insert into foo values(1);
INSERT 88959 1
test=> create table bar(id int references foo);
NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
CREATE
test=> begin;
BEGIN
test=> insert into bar values(1);
INSERT 88976 1
test=>

after that (we did not issued commit or rollback on the connection)
in another psql:

test=> begin;
BEGIN
test=> insert into bar values(1);
...and this transaction locks up until we finish first transaction

if we insert different values no locking occur.
this happens on both postgresql 7.03 and 7.1-beta1

/fjoe



pgsql-hackers by date:

Previous
From: "Rod Taylor"
Date:
Subject: Co-Location
Next
From: Tom Lane
Date:
Subject: Re: Table name scope (was Re: [BUGS] Outer joins aren't working with views)