Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Alex Hunsaker <badalex(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.
Date: 2012-01-06 16:13:40
Message-ID: 4F071DB4.10107@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 01/06/2012 10:49 AM, Alvaro Herrera wrote:
> Excerpts from Andrew Dunstan's message of vie ene 06 10:34:30 -0300 2012:
>
>> And yes, we should possibly add a regression test or two. Of course, we can't use the cause of the original complaint ($^V) in them, though.
> Why not? You obviously can't need output it verbatim, but you could
> compare it with a different function that returns $^V stringified by a
> different mechanism.
>

not sure exactly how to in such a way that exercises this code, but feel
free to suggest something ;-)

cheers

andrew

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-01-06 18:05:09 pgsql: Fix pg_restore's direct-to-database mode for INSERT-style table
Previous Message Alvaro Herrera 2012-01-06 15:49:26 Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-06 16:37:25 Re: Poorly thought out code in vacuum
Previous Message Tom Lane 2012-01-06 16:05:21 Re: CLOG contention