Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2U6FKK68590; Fri, 30 Mar 2001 01:15:21 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f2U6FGw00192; Fri, 30 Mar 2001 01:15:16 -0500 (EST) To: "Mikheev, Vadim" cc: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 In-reply-to: <3AC40890.399F5102@tpf.co.jp> References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> <3AC40890.399F5102@tpf.co.jp> Comments: In-reply-to Hiroshi Inoue message dated "Fri, 30 Mar 2001 13:16:16 +0900" Date: Fri, 30 Mar 2001 01:15:15 -0500 Message-ID: <189.985932915@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/627 X-Sequence-Number: 2298 > Just looked in heapam.c - I can fix it in two hours. > The question is - should we do this now? This scares the hell out of me. I do NOT think we should be making quick-hack changes in fundamental system semantics at this point of the release cycle. The problem went unnoticed for two full release cycles --- therefore, it can wait another cycle for a fix that has been considered, reviewed, and tested. Let's not risk making things worse by releasing a new behavior we might find out is also wrong. regards, tom lane