Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f2UEI2K49336 for ; Fri, 30 Mar 2001 09:18:02 -0500 (EST) (envelope-from pgsql-sql-owner@postgresql.org) Received: from mailer.sectorbase.com (gate1.sectorbase.com [63.88.121.2]) by postgresql.org (8.11.3/8.11.1) with SMTP id f2U3EjK49608 for ; Thu, 29 Mar 2001 22:14:45 -0500 (EST) (envelope-from vmikheev@SECTORBASE.COM) Received: (qmail 12696 invoked by uid 503); 30 Mar 2001 03:14:41 -0000 Received: from sectorbase1.sectorbase.com (192.168.254.1) by gate1.sectorbase.com with SMTP; 30 Mar 2001 03:14:41 -0000 Received: by sectorbase1.sectorbase.com with Internet Mail Service (5.5.2653.19) id ; Thu, 29 Mar 2001 19:14:40 -0800 Message-ID: <8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.sectorbase.com> From: "Mikheev, Vadim" To: "'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: Thu, 29 Mar 2001 19:14:39 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200103/638 X-Sequence-Number: 2310 > >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? Vadim