| From: | Ralph Graulich <maillist(at)shauny(dot)de> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | PostgreSQL General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Logging SQL queries? |
| Date: | 2002-07-18 12:14:58 |
| Message-ID: | Pine.LNX.4.21.0207181412170.1483-100000@shauny.shauny.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
[...]
> Has anyone else come across this or is it just me?
It's not only you. I wanted to know, why syslogd ate 70% of my CPU time
and saw that it just logs enormous amounts of data to /var/log/postgres.
So the first thing was to put a hyphen in front of the logfile's name in
/etc/syslogd.conf and the second best thing was to set the debug level of
postgres to a more sane value.
After doing this and restarting both syslogd and postgres, the performance
was five to six times better than before. So, maybe we can have a note
about that in the postgres manual?
Kind regards
... Ralph ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johnson, Shaunn | 2002-07-18 12:24:25 | Re: pg_restore: archiver error |
| Previous Message | Martijn van Oosterhout | 2002-07-18 12:10:46 | Re: Query Performance... |