Received: from acheron.rime.com.au (albatr.lnk.telstra.net [139.130.54.222]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2U4FuK55369; Thu, 29 Mar 2001 23:15:56 -0500 (EST) (envelope-from pjw@rhyme.com.au) Received: from oberon (Oberon.rime.com.au [203.8.195.100]) by acheron.rime.com.au (8.9.3/8.9.3) with SMTP id OAA20978; Fri, 30 Mar 2001 14:02:28 +1000 Message-Id: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> X-Sender: pjw@mail.rhyme.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 30 Mar 2001 14:02:28 +1000 To: "Mikheev, Vadim" , "'Hiroshi Inoue'" , Tom Lane From: Philip Warner Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 Cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.sectorb ase.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200103/626 X-Sequence-Number: 2297 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? ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/