| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> |
| Cc: | "Curt Sampson" <cjs(at)cynic(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Urgent: Tuning strategies? |
| Date: | 2002-06-25 13:56:15 |
| Message-ID: | 7219.1025013375@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> writes:
>> (RAID-5 writes tend to be very slow.) Consider adding a
>> mirrored pair of disks just for the log file.
> As far as I can see, logfile isn't a problem on debug_level 0 (which I
> always set for production state) because there's hardly anything to
> write except on vacuum analyze (which usually only takes place when
> hardly anybody does anything on the system anyway).
Curt's talking about the WAL log (pg_xlog/), not the postmaster's debug
output.
However, if your problems are with SELECTs and not with update
operations, then the WAL log is not the source of your problems anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wim | 2002-06-25 14:23:27 | Urgent... access to table failed! |
| Previous Message | Markus Wollny | 2002-06-25 13:47:43 | Re: Urgent: Tuning strategies? |