| From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: improving log management |
| Date: | 2010-01-14 03:57:39 |
| Message-ID: | 20100114125739.9A1E.52131E4D@oss.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Euler Taveira de Oliveira <euler(at)timbira(dot)com> wrote:
> other log management softwares have a way to do that so why our logger doesn't
> have such capability?
>
> I want to propose a new command to be execute after the log file is rotated. A
> GUC parameter log_after_rotation_command that takes a (set of) command(s) that
> will be executed after a log file is rotated.
If you have better loggers already, why don't you use them? In another word,
should we cooperate with them instead of re-inventing alternative loggers?
We have "Logging Brainstorm" topic in out wiki. It might help you.
http://wiki.postgresql.org/wiki/Logging_Brainstorm
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-14 04:08:54 | Re: Pretty printed trigger in psql |
| Previous Message | KaiGai Kohei | 2010-01-14 03:43:27 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |