| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Subject: | Re: WIP - syslogger infrastructure changes |
| Date: | 2009-09-25 21:18:57 |
| Message-ID: | 4008.1253913537@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ argh, hit send a bit too fast ]
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Also, how often does it actually happen that "random libraries linked
> into the backend emit messages on stderr"? Is this really something
> that we need to pay so much attention to, rather than just let them go
> on stderr and have them be redirected?
Yes, this is an ABSOLUTE deal-breaker. To name two reasons:
* glibc tells about various malloc-arena-corruption problems on stderr.
* On a lot of systems you will not find out anything useful about
dynamic-linker problems if you don't capture stderr.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-25 21:22:07 | Re: WIP - syslogger infrastructure changes |
| Previous Message | Marko Kreen | 2009-09-25 21:18:48 | Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen |