| From: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
|---|---|
| To: | "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net> |
| Cc: | 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-10 01:32:07 |
| Message-ID: | 1078882327.9858.24.camel@chinstrap |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
On Wed, 2004-03-10 at 12:09, Gavin M. Roy wrote:
> Might want to look at metalog, it does delayed writes, though ultimately
> your issue is io bound and there's not much you can do to reduce io if
> you want to keep syslog logging your pgsql queries and such.
Yeah, but syslog with fsync() after each line is much, much worse than
syslog without it, assuming anything else is on the same disk (array).
It just guarantees to screw up your drive head movements...
--
Stephen Norris srn(at)fn(dot)com(dot)au
Farrow Norris Pty Ltd +61 417 243 239
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-10 02:52:02 | Re: Restricting Groups / Users |
| Previous Message | Hadley Willan | 2004-03-10 01:21:59 | Restricting Groups / Users |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcus Andree S. Magalhaes | 2004-03-10 03:35:15 | optimizing large query with IN (...) |
| Previous Message | Gavin M. Roy | 2004-03-10 01:09:13 | Re: [PERFORM] syslog slowing the database? |