| From: | David Wheeler <david(at)wheeler(dot)net> |
|---|---|
| To: | Andrew Perrin <clists(at)perrin(dot)socsci(dot)unc(dot)edu> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Silencing NOTICEs in Perl Pg |
| Date: | 2002-08-30 16:18:18 |
| Message-ID: | 1819BC3A-BC34-11D6-B671-0003931A964A@wheeler.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Friday, August 30, 2002, at 09:01 AM, Andrew Perrin wrote:
> I don't know the Pg module at all, but if it uses warn() to dump those
> notices to STDERR, you can use a sig handler to catch them:
I actually tried that, too. It didn't work. DDB::Pg just uses libpq,
and that C library is what generates the NOTICES. I think it uses C's
printf internally, but there was no way to capture that in Perl short
of filtering STDERR's output through a forked perl or grep.
Regards,
David
--
David Wheeler AIM: dwTheory
david(at)wheeler(dot)net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory(at)jabber(dot)org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Zouroudis | 2002-08-30 16:33:02 | TG_OP and DELETE |
| Previous Message | Bruce Momjian | 2002-08-30 16:09:13 | Re: Postgres Hidden Pitfalls |