From: Herouth Maoz <herouth@oumail.openu.ac.il>
To: efte@fornax.hu
To: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] transaction-lock?
Date: Wed, 24 Mar 1999 14:42:30 +0200
Message-ID: <l03110707b31e8e019ea2@[147.233.150.135]> (raw)
In-Reply-To: <36F7D825.F3FFD86E@fornax.hu>
At 20:06 +0200 on 23/03/1999, Forgacs Tamas wrote:
>
> I am a novice pgsql user. I used Oracle, but it is unbelievable what
> bugs they have...
>
> So, is it possible, that if one transaction is pending on for eg. 'test'
> table in one psql session, then in another session this 'test' table is
> locked until the transaction is not finished on another????
>
> I have been tested a lot of ways, but the most easier problem is the
> next:
> - there is a table named 'test', with only 1 field.
> - opening a psql session on tty1, and on tty2 into the same database
>
> - on tty1 'begin' a transaction
> - on tty1 'insert' 1 row into the 'test' table
> - on tty2 'select' from the 'test' table
> => on the tty2 there is no answer until on the tty1 is the
> transaction not finished
Yes, that's the documented behaviour. Oracle has bugs, but Postgres will
have a better locking resolution only starting 6.5. At the moment it locks
on tables.
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: herouth@oumail.openu.ac.il, efte@fornax.hu
Subject: Re: [SQL] transaction-lock?
In-Reply-To: <l03110707b31e8e019ea2@[147.233.150.135]>
References: <36F7D825.F3FFD86E@fornax.hu> <l03110707b31e8e019ea2@[147.233.150.135]>
* 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