Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (8.11.3/8.11.1) with SMTP id f2U4EXK54995 for ; Thu, 29 Mar 2001 23:14:34 -0500 (EST) (envelope-from Inoue@tpf.co.jp) Received: (qmail 11358 invoked from network); 30 Mar 2001 04:14:25 -0000 Received: from unknown (HELO tpf.co.jp) (126.0.1.61) by sd2.10.0.100.in-addr.arpa with SMTP; 30 Mar 2001 04:14:25 -0000 Message-ID: <3AC40890.399F5102@tpf.co.jp> Date: Fri, 30 Mar 2001 13:16:16 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Philip Warner CC: "Mikheev, Vadim" , Tom Lane , pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200103/625 X-Sequence-Number: 2296 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