Received: from haven.fornet (gw0.fornax.hu [195.228.35.1]) by hub.org (8.9.2/8.9.1) with ESMTP id NAA99376 for ; Tue, 23 Mar 1999 13:05:18 -0500 (EST) (envelope-from efte@fornax.hu) Received: from fornax.hu (forgacs.fornet [192.168.215.104]) by haven.fornet (8.9.1a/8.9.0) with ESMTP id TAA25574 for ; Tue, 23 Mar 1999 19:04:59 +0100 Message-ID: <36F7D825.F3FFD86E@fornax.hu> Date: Tue, 23 Mar 1999 19:06:29 +0100 From: Forgacs Tamas Reply-To: efte@fornax.hu Organization: Fornax Co. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: transaction-lock? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, 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 This runs on the next architecture (compiled today the new 6.4 release!): - IP133, 49M RAM - Debian 2.0 If I have been a inattentive then please send me the solution, and sorry; if not, then please send me the solution, and 'not at all'. FT