| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Spiegelberg <gspiegelberg(at)cranel(dot)com>, PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>, Postgres Admin List <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] syslog slowing the database? |
| Date: | 2004-03-15 15:17:49 |
| Message-ID: | Pine.LNX.4.33.0403150816410.6471-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
On Thu, 11 Mar 2004, Christopher Kings-Lynne wrote:
> > You could also consider not using syslog at all: let the postmaster
> > output to its stderr, and pipe that into a log-rotation program.
> > I believe some people use Apache's log rotator for this with good
> > results.
>
> Not an option I'm afraid. PostgreSQL just jams and stops logging after
> the first rotation...
>
> I've read in the docs that syslog logging is the only "production"
> solution...
Can you use the apache log rotator? It's known to work in my environment
(redhat 7.2, postgresql 7.2 and 7.4) with this command to start it in my
rc.local file:
su - postgres -c 'pg_ctl start | rotatelogs $PGDATA/pglog 86400 2>1&'
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-15 15:38:02 | Re: [PERFORM] syslog slowing the database? |
| Previous Message | Bruce Momjian | 2004-03-15 14:06:01 | Re: pgcheck ?? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-15 15:38:02 | Re: [PERFORM] syslog slowing the database? |
| Previous Message | Arjen van der Meijden | 2004-03-14 23:21:17 | Re: Large CASE-statement is pretty slow? |