Re: unlock Select for update - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: unlock Select for update
Date
Msg-id 20030311090115.GB5057@svana.org
Whole thread Raw
In response to Re: unlock Select for update  ("jose antonio leo" <jaleo8@storelandia.com>)
Responses Re: unlock Select for update
List pgsql-general
On Tue, Mar 11, 2003 at 09:10:21AM +0100, jose antonio leo wrote:
> Unfortunately In my aplication this non occur . When the client disconnects
> the row keep blocked and then I have kill the process manually for unlocked
> the row.
>
> You know why it happends?

You're obviously doing something wrong, since if the client disconnected,
then there would be nothing to kill. You'll need to explain more about your
system before we can help you.

> -----Mensaje original-----
> De: Neil Conway [mailto:neilc@samurai.com]
> Enviado el: lunes, 10 de marzo de 2003 19:05
> Para: jose antonio leo
> CC: Bruce Momjian; pgsql-general
> Asunto: RE: [GENERAL] unlock Select for update
>
>
> On Mon, 2003-03-10 at 12:15, jose antonio leo wrote:
> > Sorry, I explain more...
> > I have got a aplication that it do maintenance of DB, One user are
> updating
> > a row locked for a select for update and this user switch off your pc and
> he
> > leaves the row locked.
>
> When the client disconnects, any uncommitted transaction (if any) will
> be aborted, so the lock will be released.
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Support bacteria! They're the only culture some people have.

Attachment

pgsql-general by date:

Previous
From: "jose antonio leo"
Date:
Subject: Re: unlock Select for update
Next
From: Jason Godden
Date:
Subject: Re: BLOBS (ODBC lo object) and pg_restore