Forest Wilkinson <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
- RE: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Philip Warner
- Re: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Hiroshi Inoue
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Philip Warner
- RE: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Philip Warner
- Re: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Tom Lane
- RE: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Mikheev, Vadim
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Hiroshi Inoue
- Re: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Forest Wilkinson
- RE: [HACKERS] Re: [SQL] possible row locking bug in 7.0.3... Mikheev, Vadim