From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Optimizing a huge_table/tiny_table join
Date: Thu, 25 May 2006 12:48:40 -0400
Message-ID: <20060525164840.GA2954@phlogiston.dyndns.org> (raw)
In-Reply-To: <200605251631.k4PGV4O28645@panix3.panix.com>
References: <200605251631.k4PGV4O28645@panix3.panix.com>
On Thu, May 25, 2006 at 12:31:04PM -0400, kynn@panix.com wrote:
> Well, they're not my statistics; they're explain's. You mean there's
Explain doesn't get them from nowhere. How often is the table being
ANALYSEd?
> More bewildering still (and infuriating as hell--because it means that
> all of my work for yesterday has been wasted) is that I can no longer
> reproduce the best query plan I posted earlier, even though the tables
> have not changed at all. (Hence I can't post the explain analyze for
I find that very hard to believe. Didn't change _at all_? Are you
sure no VACUUMs or anything are happening automatically?
> Anyway, I take it that there is no way to bypass the optimizer and
> instruct PostgreSQL exactly how one wants the search performed?
No, there isn't.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
The fact that technology doesn't work is no bar to success in the marketplace.
--Philip Greenspun
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: Optimizing a huge_table/tiny_table join
In-Reply-To: <20060525164840.GA2954@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