Skip site navigation (1) Skip section navigation (2)

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 15:49:26
Message-ID: 1325864888-sup-1128@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-01-06 15:51:05
Subject: Re: Poorly thought out code in vacuum
Previous:From: Robert HaasDate: 2012-01-06 15:49:14
Subject: Re: Progress on fast path sorting, btree index creation time

pgsql-committers by date

Next:From: Andrew DunstanDate: 2012-01-06 16:13:40
Subject: Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.
Previous:From: Robert HaasDate: 2012-01-06 13:36:27
Subject: pgsql: Fix variable confusion in BufferSync().

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group