From: | Luís Silva <lfs12(at)hotmail(dot)com> |
---|---|
To: | "'Bruno Wolff III'" <bruno(at)wolff(dot)to>, "'Christian Hofmann'" <christian(dot)hofmann(at)gmx(dot)de> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: SELECT FOR UPDATE - release lock? |
Date: | 2006-05-05 13:49:25 |
Message-ID: | BAY117-DAV16DACD6A29D96EEA9B7D93B5B50@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Locks only affects the lines in the table selected in the sql query, right?
-----Mensagem original-----
De: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] Em nome de Bruno Wolff III
Enviada: quinta-feira, 4 de Maio de 2006 20:21
Para: Christian Hofmann
Cc: pgsql-novice(at)postgresql(dot)org
Assunto: Re: [NOVICE] SELECT FOR UPDATE - release lock?
On Thu, May 04, 2006 at 22:08:16 +0200,
Christian Hofmann <christian(dot)hofmann(at)gmx(dot)de> wrote:
> Hello,
>
> for some tables I am using a "select a,b,c from mytable where x='abc' FOR
> UPDATE" query to prevent other servers also modify this data while I am
> reading the data and decide to modify the data.
>
> Now sometimes I don't want to make an update. Is there a way to release
the
> lock. Or is the lock released by simply call commit?
Locks are released when transactions end.
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2006-05-05 14:03:04 | Re: SELECT FOR UPDATE - release lock? |
Previous Message | Joao Miguel Ferreira | 2006-05-05 12:30:46 | what are the pg_clog and pg_xlog directories ? |