Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2UNlQK57673; Fri, 30 Mar 2001 18:47:26 -0500 (EST) (envelope-from fspam@home.com) Received: from bartok ([24.9.226.149]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010330234723.STCX14080.femail13.sdc1.sfba.home.com@bartok>; Fri, 30 Mar 2001 15:47:23 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Forest Wilkinson To: Tom Lane , "Mikheev, Vadim" Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 Date: Fri, 30 Mar 2001 15:47:22 -0800 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> <3AC40890.399F5102@tpf.co.jp> <189.985932915@sss.pgh.pa.us> In-Reply-To: <189.985932915@sss.pgh.pa.us> MIME-Version: 1.0 Message-Id: <01033015472200.01012@bartok> Content-Transfer-Encoding: 8bit X-Archive-Number: 200103/652 X-Sequence-Number: 2331 On Thursday 29 March 2001 22:15, Tom Lane wrote: > > 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. Although I'm the one who is being bit by this bug, I tend to agree. > The problem went unnoticed for two full release cycles I first reported the problem on 25 September 2000, on the pgsql-sql list, message subject "SQL functions not locking properly?" I was using 7.0.2 at the time. Also, I seem to remember that a problem of this nature bit me in 6.5.x as well. > 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. Good point. How long is the next cycle likely to take? Forest