| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: log_filename_prefix --> log_filename + strftime() |
| Date: | 2004-08-28 19:50:44 |
| Message-ID: | 4130E214.9050400@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
> It's definitely creeping featurism ... but
> I can see the value of not needing any cron daemon to remove old logs.
No other logs on your system to purge?
>
> A potential problem is what about size-driven rotation? If the hourly
> output exceeds log_rotation_size then you'd truncate and rewrite the
> current file, which is just exactly not what you want :-(.
Same can happen after logger process restart.
After all, I wonder what an apache style logfile name is good for. The
pgsql logfiles don't contain access log data that are analyzed by
webalizer or stuff like that. I don't see the point having any
formatting option at all.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Bertheau | 2004-08-28 20:09:20 | Re: [SQL] array_in: '{}}'::text[] |
| Previous Message | Joe Conway | 2004-08-28 19:33:35 | Re: [SQL] array_in: '{}}'::text[] |