Re: It's June 1; do you know where your release is?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: It's June 1; do you know where your release is?
Date: 2009-06-05 05:04:55
Message-ID: 26354.1244178295@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Jun 4, 2009, at 3:58 PM, Tom Lane wrote:
>> It seems we have two reasonable possibilities for 8.4: revert that
>> patch and keep contrib/intarray's behavior the same as it was, or leave the
>> patch in and document that there was a behavioral change.

> You can't keep the patch and update intarray to behave like it did
> before?

Uh, no. The point is that intarray's operators behave(d) differently
from the core operators.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2009-06-05 06:14:29 Re: postmaster recovery and automatic restart suppression
Previous Message Jeremy Kerr 2009-06-05 04:04:00 Re: [RFC, PATCH] Avoid manual shift-and-test logic in AllocSetFreeIndex