From: Ludwig Lim <lud_nowhere_man@yahoo.com>
To: PostgreSQL Mailing List <pgsql-sql@postgresql.org>
Subject: Locking that will delayed a SELECT
Date: Wed, 16 Oct 2002 04:40:43 -0700 (PDT)
Message-ID: <20021016114043.84798.qmail@web80305.mail.yahoo.com> (raw)
Hi:
Suppose I have a transaction (T1) which executes a
complicated stored procedure. While T1 is executing,
trasaction #2 (T2) begins to execute.
T1 take more time to execute that T2 in such a way
that T2 finished earlier than T1. The result is that
t2 returns set of data before it can be modified by
T1.
Given the above scenario. Is there a way such that
while T2 will only read that value updated by T1 (i.e.
T2 must wait until T1 is finished) ? What locks should
I used since a portion of T1 contains SELECT
statements? Should I used the "SERIALIZABLE
isolation".
Thank you in advance.
ludwig.
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: lud_nowhere_man@yahoo.com
Subject: Re: Locking that will delayed a SELECT
In-Reply-To: <20021016114043.84798.qmail@web80305.mail.yahoo.com>
* 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