From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-11 01:34:54 |
Message-ID: | 404FC23E.9000207@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
> 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...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Smith | 2004-03-11 01:37:38 | Re: [PERFORM] syslog slowing the database? |
Previous Message | Vivek Khera | 2004-03-10 21:00:36 | Re: syslog slowing the database? |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Smith | 2004-03-11 01:37:38 | Re: [PERFORM] syslog slowing the database? |
Previous Message | Joseph Shraibman | 2004-03-11 00:43:57 | Re: Postgresql on SAN |