Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2V01gK59677; Fri, 30 Mar 2001 19:01:42 -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 f2V01Rw19650; Fri, 30 Mar 2001 19:01:27 -0500 (EST) To: Forest Wilkinson cc: "Mikheev, Vadim" , 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: <01033015472200.01012@bartok> References: <3.0.5.32.20010330140228.01f9d100@mail.rhyme.com.au> <3AC40890.399F5102@tpf.co.jp> <189.985932915@sss.pgh.pa.us> <01033015472200.01012@bartok> Comments: In-reply-to Forest Wilkinson message dated "Fri, 30 Mar 2001 15:47:22 -0800" Date: Fri, 30 Mar 2001 19:01:27 -0500 Message-ID: <19647.985996887@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/653 X-Sequence-Number: 2332 Forest Wilkinson writes: > Good point. How long is the next cycle likely to take? Good question. I'd like to say 4 to 6 months, but that was how long 7.1 was supposed to take, and we're pushing a year now. What might make the most sense is to develop and test a fix in the early part of the 7.2 development cycle, and then back-patch it into a 7.1.x release perhaps 2 or 3 months from now. regards, tom lane