Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.2/8.9.1) with ESMTP id HAA23078 for ; Wed, 24 Mar 1999 07:41:10 -0500 (EST) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id 9563E4B4A1; Wed, 24 Mar 1999 14:41:06 +0200 (IST) Received: from [147.233.150.135] (1671.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA6DD3; Wed, 24 Mar 1999 14:42:50 +0200 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <36F7D825.F3FFD86E@fornax.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 24 Mar 1999 14:42:30 +0200 To: efte@fornax.hu, pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: Re: [SQL] transaction-lock? 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