Re: [COMMITTERS] pgsql: Clean up package namespace use and use of Safe in plperl.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Clean up package namespace use and use of Safe in plperl.
Date: 2010-02-17 04:53:30
Message-ID: 15986.1266382410@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

adunstan(at)postgresql(dot)org (Andrew Dunstan) writes:
> Clean up package namespace use and use of Safe in plperl.

According to buildfarm member kite, there is more than one spelling of
the Perl warning message that was (randomly?) chosen for the test added
here. I doubt it's worth maintaining a variant expected file for this
--- I'd suggest picking a simpler warning or dropping the actual
warning-generation aspect of the test.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2010-02-17 05:32:49 pgsql: Use a fatal warning check with what looks like a more portable
Previous Message User Itagaki 2010-02-17 04:35:21 pgstatsinfo - pg_statsinfo: Logger should not shutdown before any other

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-02-17 05:13:51 Re: bug? autovacuum is not launched even if autovacuum_freeze_max_age is reached
Previous Message James William Pye 2010-02-17 03:55:11 Re: Tightening binary receive functions