From: Forgacs Tamas <efte@fornax.hu>
To: pgsql-sql@postgresql.org
Subject: transaction-lock?
Date: Tue, 23 Mar 1999 19:06:29 +0100
Message-ID: <36F7D825.F3FFD86E@fornax.hu> (raw)
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
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: efte@fornax.hu
Subject: Re: transaction-lock?
In-Reply-To: <36F7D825.F3FFD86E@fornax.hu>
References: <36F7D825.F3FFD86E@fornax.hu>
* 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