From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Some queries starting to hang
Date: Mon, 5 Jun 2006 16:38:51 -0400
Message-ID: <20060605203851.GB7071@phlogiston.dyndns.org> (raw)
In-Reply-To: <22706.1149538039@sss.pgh.pa.us>
References: <1149534308.3583.56.camel@bg002441.pro-unlimited.com>
<22706.1149538039@sss.pgh.pa.us>
On Mon, Jun 05, 2006 at 04:07:19PM -0400, Tom Lane wrote:
>
> broke:
> > -> Nested Loop (cost=30150.77..129334.04 rows=1 width=305)
>
> work:
> > -> Hash Join (cost=30904.77..125395.89 rows=1810 width=306)
>
> 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?
(I've _had_ bad plans that picked nestloop, for sure, but they're
usually for tens of thousands of rows when they take forever).
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Users never remark, "Wow, this software may be buggy and hard
to use, but at least there is a lot of code underneath."
--Damien Katz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Some queries starting to hang
In-Reply-To: <20060605203851.GB7071@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox