| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Subject: | Re: WIP - syslogger infrastructure changes |
| Date: | 2009-09-15 06:03:17 |
| Message-ID: | 20090915145538.9C68.52131E4D@oss.ntt.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On 15 sep 2009, at 07.21, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp
> > I'd like to have an opposite approach -- per-backend log files.
>
> I can see each backend writing it, certainly, but keeping it in
> separate files makes it useless without post processing, which in most
> vases means useless for day-to-day work.
Sure. There should be a trade-off between performance and usability.
And that's is the reason I submitted per-destination or per-category
log filter. Log messages for "day-to-day work" should be written in
a single file (either text or syslog), but sql queries used only for
database auditing are acceptable even if written in separate files.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-09-15 06:32:48 | Re: Streaming Replication patch for CommitFest 2009-09 |
| Previous Message | Stefan Kaltenbrunner | 2009-09-15 05:48:26 | Re: CommitFest 2009-09: Now In Progress |