Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 8890E634FC8 for ; Thu, 4 Jun 2009 11:53:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 28041-07 for ; Thu, 4 Jun 2009 11:52:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by mail.postgresql.org (Postfix) with ESMTP id C095E634E44 for ; Thu, 4 Jun 2009 11:53:02 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-027.nc.res.rr.com [::ffff:75.177.154.27]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Thu, 04 Jun 2009 10:52:44 -0400 id 000806DC.4A27DFBD.00001F03 Message-ID: <4A27DFC2.8040004@dunslane.net> Date: Thu, 04 Jun 2009 10:52:50 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Tom Lane CC: Magnus Hagander , Dave Page , Josh Berkus , PostgreSQL-development Subject: Re: It's June 1; do you know where your release is? References: <19107.1243873940@sss.pgh.pa.us> <603c8f070906012050p6ccd62d3v13d3e0f887fe7c90@mail.gmail.com> <15765.1243965376@sss.pgh.pa.us> <4A25C32F.30203@agliodbs.com> <4A25C9A9.5010303@dunslane.net> <4A25D91B.5080401@dunslane.net> <4A26FF38.8090308@dunslane.net> <937d27e10906031610g341525e5j9414d8af3d8f293c@mail.gmail.com> <4A270A06.1010507@dunslane.net> <937d27e10906040249u73ac21dds6057300011d38a2d@mail.gmail.com> <4A27AA1D.6000800@hagander.net> <4A27C1BB.7080909@dunslane.net> <13402.1244124741@sss.pgh.pa.us> In-Reply-To: <13402.1244124741@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.097 tagged_above=0 required=5 tests=AWL=0.097 X-Spam-Level: X-Archive-Number: 200906/421 X-Sequence-Number: 139476 Tom Lane wrote: > Andrew Dunstan 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