Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 - Mailing list pgsql-sql

From Hiroshi Inoue
Subject Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date
Msg-id 3AC40890.399F5102@tpf.co.jp
Whole thread Raw
Responses Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-sql
Philip Warner wrote:
> 
> At 19:14 29/03/01 -0800, Mikheev, Vadim wrote:
> >> >Reported problem is caused by bug (only one tuple version must be
> >> >returned by SELECT) and this is way to fix it.
> >> >
> >>
> >> I assume this is not possible in 7.1?
> >
> >Just looked in heapam.c - I can fix it in two hours.
> >The question is - should we do this now?
> >Comments?
> 
> It's a bug; how confident are you of the fix?
> 

I doubt if it's a bug of SELECT. Well what
'concurrent UPDATE then SELECT FOR UPDATE +
SELECT' return ?

regards,
Hiroshi Inoue


pgsql-sql by date:

Previous
From: Philip Warner
Date:
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Next
From: Philip Warner
Date:
Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1