From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Rosser Schwarz" <rschwarz(at)totalcardinc(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: atrocious update performance |
Date: | 2004-03-16 22:29:53 |
Message-ID: | 294.1079476193@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Rosser Schwarz" <rschwarz(at)totalcardinc(dot)com> writes:
> Having never more than glanced at the output of "vacuum verbose", I
> can't say whether that makes the cut for oodles. My suspicion is no.
Nope, it sure doesn't. We occasionally see people who don't know they
need to vacuum regularly and have accumulated hundreds or thousands of
dead tuples for every live one :-(. That's clearly not the issue here.
I'm fresh out of ideas, and the fact that this is a live server kinda
limits what we can do experimentally ... but clearly, *something* is
very wrong.
Well, when you don't know what to look for, you still have to look.
One possibly useful idea is to trace the kernel calls of the backend
process while it does that ridiculously long EXPLAIN --- think you could
try that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rosser Schwarz | 2004-03-17 00:20:39 | Re: atrocious update performance |
Previous Message | Rosser Schwarz | 2004-03-16 22:18:41 | Re: atrocious update performance |