Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Forest Wilkinson <fspam(at)home(dot)com>
Cc: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1
Date: 2001-03-31 00:01:27
Message-ID: 19647.985996887@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

Forest Wilkinson <fspam(at)home(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Franck Martin 2001-03-31 00:02:35 Re: Third call for platform testing (linux 2.4.x)
Previous Message Forest Wilkinson 2001-03-30 23:47:22 Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2001-03-31 01:14:50 Re: [SQL] Re: pg_dump potential bug -UNIQUE INDEX on PG_SHADOW Dont!! HELP
Previous Message Forest Wilkinson 2001-03-30 23:47:22 Re: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1