From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Spiegelberg <gspiegelberg(at)cranel(dot)com> |
Cc: | PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>, Postgres Admin List <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: syslog slowing the database? |
Date: | 2004-03-10 16:53:51 |
Message-ID: | 7688.1078937631@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
Greg Spiegelberg <gspiegelberg(at)cranel(dot)com> writes:
> If the log and database were on the same disk I'd be okay with the
> current workaround. If the ``-'' gave me near the same performance as
> turning syslog off I'd be okay with that too. However, neither of these
> are the case so there has to be something else blocking between the two
> processes.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-03-10 17:12:27 | Re: Hardware for a database server |
Previous Message | William Yu | 2004-03-10 16:41:29 | Re: Hardware for a database server |
From | Date | Subject | |
---|---|---|---|
Next Message | Marcus Andree S. Magalhaes | 2004-03-10 17:02:23 | Re: optimizing large query with IN (...) |
Previous Message | scott.marlowe | 2004-03-10 16:47:09 | Re: optimizing large query with IN (...) |