Re: It's June 1; do you know where your release is? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: It's June 1; do you know where your release is?
Date
Msg-id 13402.1244124741@sss.pgh.pa.us
Whole thread Raw
In response to Re: It's June 1; do you know where your release is?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: It's June 1; do you know where your release is?
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PANIC: corrupted item lengths
Next
From: Tom Lane
Date:
Subject: Re: Improving the ngettext() patch