| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Smith <john_smith_45678(at)yahoo(dot)com> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: UPDATE slow |
| Date: | 2003-02-05 07:44:26 |
| Message-ID: | 23032.1044431066@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John Smith <john_smith_45678(at)yahoo(dot)com> writes:
> Here are my postgresql.conf settings (I just uncommented the mentioned vars and restarted):
> shared_buffers = 64 # 2*max_connections, min 16, typically 8KB each
There's your problem, or part of it anyway. That's not enough buffers
to manipulate a bunch of indexes efficiently. Production-grade settings
for shared_buffers are more like 1 to 10 thousand.
> max_fsm_relations = 100 # min 10, fsm is free space map, ~40 bytes
> max_fsm_pages = 10000 # min 1000, fsm is free space map, ~6 bytes
You probably will want to jack those up too.
> sort_mem = 1024 # min 64, size in KB
And possibly that, though I don't think it affects this particular
query.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | roverr | 2003-02-05 11:46:35 | Question: unique on multiple columns |
| Previous Message | Tom Lane | 2003-02-05 07:34:32 | Re: not exactly a bug report, but surprising behaviour |