| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Lamar Owen <lowen(at)pari(dot)edu>, Fernando Nasser <fnasser(at)redhat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Log rotation |
| Date: | 2004-03-13 15:45:35 |
| Message-ID: | 1079192734.736.33.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I can see that in a multipostmaster setting how you might want some
> > differentiation between postmasters, but ISTM that the tool reading these
> > logs should be trained in how to separate loglines out. <snip>
>
> Different postmasters = different conf files. Just set your syslog_facility
> and/or your syslog_ident differently and it should be pretty easy to seperate
> the logs. Actually, now that I have started using syslog fairly regularly, I
Not that I'm volunteering, but I think the biggest issue is many users
simply don't know how to approach the problem. Some docs on using
syslog, cron, etc. with PostgreSQL to accomplish maintenace jobs would
probably be enough.
The only mention we have of syslog is related to the postgresql.conf
entries and their appropriate values.
http://www.postgresql.org/docs/7.4/static/runtime-config.html#RUNTIME-CONFIG-LOGGING-SYSLOG
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fernando Nasser | 2004-03-13 15:46:40 | Re: Log rotation |
| Previous Message | Tom Lane | 2004-03-13 15:39:39 | Re: rapid degradation after postmaster restart |