| From: | "jose antonio leo" <jaleo8(at)storelandia(dot)com> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: unlock Select for update |
| Date: | 2003-03-11 08:10:21 |
| Message-ID: | KAEFLIDKHEJNPPKOLGHMGEIBCPAA.jaleo8@storelandia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
-----Mensaje original-----
De: Neil Conway [mailto:neilc(at)samurai(dot)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(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2003-03-11 09:01:16 | Re: unlock Select for update |
| Previous Message | Holger Klawitter | 2003-03-11 07:05:46 | store not available |