Skip site navigation (1) Skip section navigation (2)

Re: Optimizing a huge_table/tiny_table join

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Optimizing a huge_table/tiny_table join
Date: 2006-05-25 16:48:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Thu, May 25, 2006 at 12:31:04PM -0400, kynn(at)panix(dot)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

> 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.  


Andrew Sullivan  | ajs(at)crankycanuck(dot)ca
The fact that technology doesn't work is no bar to success in the marketplace.
		--Philip Greenspun

In response to

pgsql-performance by date

Next:From: Michael FuhrDate: 2006-05-25 16:54:56
Subject: Re: lowering priority automatically at connection
Previous:From: Chris MairDate: 2006-05-25 16:35:28
Subject: Re: lowering priority automatically at connection

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group