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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: It's June 1; do you know where your release is?
Date: 2009-06-04 14:52:50
Message-ID: 4A27DFC2.8040004@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> I have cleaned up the patch from yesterday slightly, too. I'm wondering
>> how far back we should backpatch all this. This API was actually
>> documented in Perl (just) before 7.4 was released, so in theory the API
>> adjustment should go all the way back. However, in practice it hasn't
>> been a problem until now, and we aren't supporting Windows releases
>> before 8.2, so I think 8.2 is probably the right spot.
>>
>
> My inclination is "backpatch all the way". Now that we know the problem
> is we are failing to adhere to Perl's published API, I bet we could find
> some other problems it causes, if we poked into the right nooks and
> crannies. And not just on Windows.
>
>

Yeah, the debian bug specifically mentions hppa. I'll go with your instinct.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-06-04 15:32:22 Re: User-facing aspects of serializable transactions
Previous Message Tom Lane 2009-06-04 14:52:27 Re: Improving the ngettext() patch