| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| 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-11 02:03:46 |
| Message-ID: | 20040311020346.GA13391@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
On Thu, Mar 11, 2004 at 09:34:54 +0800,
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> 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...
I use multilog to log postgres' output and it works fine.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vickriz Buenaventuura | 2004-03-11 03:32:18 | pgadmin3 software dependencies? |
| Previous Message | Chris Smith | 2004-03-11 01:37:38 | Re: [PERFORM] syslog slowing the database? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-11 04:09:41 | Re: [PERFORM] syslog slowing the database? |
| Previous Message | Chris Smith | 2004-03-11 01:37:38 | Re: [PERFORM] syslog slowing the database? |