pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Forest Wilkinson <fspam@home.com>
Cc: Mikheev, Vadim <vmikheev@SECTORBASE.COM>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date: Fri, 30 Mar 2001 19:01:27 -0500
Message-ID: <19647.985996887@sss.pgh.pa.us> (raw)
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>

Forest Wilkinson <fspam@home.com> 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



view thread (21+ messages)  latest in thread

Message-ID: <19647.985996887@sss.pgh.pa.us>
Permalink:  ../19647.985996887@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19647.985996887@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, fspam@home.com, vmikheev@SECTORBASE.COM, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
  In-Reply-To: <19647.985996887@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox