| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Louis-Marie Croisez <louis-marie(dot)croisez(at)etca(dot)alcatel(dot)be> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: access time performance problem |
| Date: | 2002-10-10 15:34:01 |
| Message-ID: | Pine.LNX.4.33.0210100929590.30553-100000@css120.ihs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 10 Oct 2002, Louis-Marie Croisez wrote:
> Sorry, bad url:
> use this instead:
> http://louis.croisez.free.fr/capture1.jpg
I'm gonna make a guess here that it's WAL activity, or log activity.
So first off, are you saving postgresql's output to a log? if so, try
logging to a different drive than your data drive or turning off logging
for a quick test.
If it's WAL writes that are causing the problem, you can either try to
change the settings for commit_delay and commit_siblings or symlinking the
pg_xlog directory somewhere else. If you aren't sure how to do that,
don't learn how to on a live production server with real data.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2002-10-10 15:34:58 | Re: connection watchdog |
| Previous Message | Shridhar Daithankar | 2002-10-10 15:33:56 | Re: Getting tables, procedures, etc. |
