Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4MEaxA87477 for ; Tue, 22 May 2001 10:36:59 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from mailer.sectorbase.com (mailer.sectorbase.com [63.88.121.2]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4J0TmA41258 for ; Fri, 18 May 2001 20:29:48 -0400 (EDT) (envelope-from vmikheev@SECTORBASE.COM) Received: (qmail 65984 invoked by uid 503); 19 May 2001 00:29:44 -0000 Received: from sectorbase2.sectorbase.com (192.168.254.2) by gate1.sectorbase.com with SMTP; 19 May 2001 00:29:44 -0000 Received: by sectorbase2.sectorbase.com with Internet Mail Service (5.5.2653.19) id ; Fri, 18 May 2001 17:28:54 -0700 Message-ID: <3705826352029646A3E91C53F7189E3201662D@sectorbase2.sectorbase.com> From: "Mikheev, Vadim" To: "'Forest Wilkinson'" , Philip Warner , "'Hiroshi Inoue'" , Tom Lane Cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 Date: Fri, 18 May 2001 17:28:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200105/245 X-Sequence-Number: 3065 > I see postgres 7.1.1 is out now. Was the fix for this > problem included in the new release? I fear it will be in 7.2 only. > 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? > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >