Locking that will delayed a SELECT

From: Ludwig Lim <lud_nowhere_man(at)yahoo(dot)com>
To: PostgreSQL Mailing List <pgsql-sql(at)postgresql(dot)org>
Subject: Locking that will delayed a SELECT
Date: 2002-10-16 11:40:43
Message-ID: 20021016114043.84798.qmail@web80305.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


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

Browse pgsql-sql by date

  From Date Subject
Next Message alexandre :: aldeia digital 2002-10-16 11:57:18 pg_atoi() error
Previous Message Albrecht Berger 2002-10-16 10:07:59 replace null with 0 in subselect ?