| From: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de> |
|---|---|
| To: | lud_nowhere_man(at)yahoo(dot)com |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Locking that will delayed a SELECT |
| Date: | 2002-10-18 07:33:09 |
| Message-ID: | 3DAFB935.5E6980B1@rodos.fzk.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> 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".
What's wrong about this question?
I'm interested in an answer, too.
Regards, Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleus Mantzios | 2002-10-18 08:19:14 | Re: Locking that will delayed a SELECT |
| Previous Message | Brian Blaha | 2002-10-18 07:19:50 | UPDATE: Apparent referential integrity bug in PL/pgSQL |