Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4H2J2A10127; Wed, 16 May 2001 22:19:02 -0400 (EDT) (envelope-from fspam@home.com) Received: from bartok ([24.9.226.149]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010517021851.UATU21661.femail4.sdc1.sfba.home.com@bartok>; Wed, 16 May 2001 19:18:51 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Forest Wilkinson To: Philip Warner , "Mikheev, Vadim" , "'Hiroshi Inoue'" , Tom Lane Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 Date: Wed, 16 May 2001 19:18:51 -0700 X-Mailer: KMail [version 1.2] Cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> In-Reply-To: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> MIME-Version: 1.0 Message-Id: <01051619185100.01497@bartok> Content-Transfer-Encoding: 8bit X-Archive-Number: 200105/181 X-Sequence-Number: 2998 I see postgres 7.1.1 is out now. Was the fix for this problem included in the new release? On Thursday 29 March 2001 20:02, 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?