| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Jonathan Ellis" <jonathan(at)utahpython(dot)org>, "smiley2211" <smiley2211(at)yahoo(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How to ENABLE SQL capturing??? |
| Date: | 2007-08-13 16:02:41 |
| Message-ID: | 87vebjqv6m.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> If I recall correctly, it is because syslog is blocking.
Are you sure it isn't just that syslog fsyncs its log files after every log
message? I don't think the individual syslogs are synchronous but if syslog
falls behind the buffer will fill and throttle the sender.
If your Postgres data is on the same device as the syslogs those fsyncs will
probably cause a big slowdown directly on Postgres's I/O as well.
You can turn off the fsyncs in syslog by putting a - before the filename.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-08-13 16:15:35 | Re: How to ENABLE SQL capturing??? |
| Previous Message | Joshua D. Drake | 2007-08-13 15:42:50 | Re: How to ENABLE SQL capturing??? |