Re: pgsql: Properly handle empty arrays returned from plperl functions.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Pg Committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Properly handle empty arrays returned from plperl functions.
Date: 2011-08-17 16:53:42
Message-ID: 1313599947-sup-782@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Excerpts from Andrew Dunstan's message of mié ago 17 12:41:47 -0400 2011:
>
> Wow, sorry for the noise. I guess I'll be more careful about reusing a
> commit-message file.

Happened to me once too (back when we used CVS). It seems the filter to
remove unwanted lines is not applied when the file is specified in the
command line which seems a bit silly to me.

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2011-08-17 17:29:01 Re: pgsql: Properly handle empty arrays returned from plperl functions.
Previous Message Andrew Dunstan 2011-08-17 16:41:47 Re: pgsql: Properly handle empty arrays returned from plperl functions.