From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Some queries starting to hang |
Date: | 2006-06-05 21:06:31 |
Message-ID: | 23915.1149541591@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Mon, Jun 05, 2006 at 04:07:19PM -0400, Tom Lane wrote:
>> I'm wondering about out-of-date or nonexistent ANALYZE stats, missing
>> custom adjustments of statistics target settings, etc.
> But even the nested loop shouldn't be a "never returns" case, should
> it? For 1800 rows?
Well, it's a big query. If it ought to take a second or two, and
instead is taking an hour or two (1800 times the expected runtime), that
might be close enough to "never" to exhaust Chris' patience. Besides,
we don't know whether the 1800 might itself be an underestimate (too bad
Chris didn't provide EXPLAIN ANALYZE results). The hash plan will scale
to larger numbers of rows much more gracefully than the nestloop ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2006-06-05 21:26:56 | Re: How to force Postgres to use index on ILIKE |
Previous Message | Andrew Sullivan | 2006-06-05 20:41:51 | Re: vacuuming problems continued |