| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <jim(at)nasby(dot)net>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warn in plperl logs as... NOTICE?? |
| Date: | 2010-01-22 03:46:33 |
| Message-ID: | 254C833B-5908-48CC-8E6C-C6336A07FCBD@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 21, 2010, at 4:55 PM, Andrew Dunstan wrote:
> *shrug* I don't have a strong opinion about it, and it's pretty easy to change, if there's a consensus we should. I have certainly found over the years that perl warnings from some modules can be annoyingly verbose, which is probably why the original patch didn't make them have a higher level in Postgres. If this were a big issue we'd have surely heard about it before now - there are plenty of plperl users out there.
Using elog(WARNING) certainly makes a lot more sense to me…
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-22 04:34:41 | Re: quoting psql varible as identifier |
| Previous Message | Kevin Grittner | 2010-01-22 02:31:11 | Re: commit fests (was Re: primary key error message) |