| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-01-06 16:13:40 | Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix. |
| Previous Message | Robert Haas | 2012-01-06 13:36:27 | pgsql: Fix variable confusion in BufferSync(). |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-01-06 15:51:05 | Re: Poorly thought out code in vacuum |
| Previous Message | Robert Haas | 2012-01-06 15:49:14 | Re: Progress on fast path sorting, btree index creation time |