Re: How to use read uncommitted transaction level and set update order

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Andrus <kobruleht2(at)hot(dot)ee>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to use read uncommitted transaction level and set update order
Date: 2009-12-19 21:35:27
Message-ID: 3073cc9b0912191335h49f884b7he3c0459872ce9968@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/12/19 Andrus <kobruleht2(at)hot(dot)ee>:
>
> set transaction isolation level read uncommitted;

the "isolation level" is for specifying what rows are visible no for columns.
besides, postgres doesn't implement "read uncommitted"

> update test1 set a=4, b=a ;
>
> b value is 1 but must be 4.

no. b value "must be" 1, you want it to be 4...
in an update the columns always hold the old value until the statement
is finished, the only way i can think for doing this is with a trigger

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2009-12-19 21:53:08 Re: How to use read uncommitted transaction level and set update order
Previous Message Jaime Casanova 2009-12-19 21:20:24 Re: alter table performance