Re: Incorrect estimates on correlated filters - Mailing list pgsql-performance

From Gregory Stark
Subject Re: Incorrect estimates on correlated filters
Date
Msg-id 878wuzvrbj.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Incorrect estimates on correlated filters  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-performance
"Craig Ringer" <craig@postnewspapers.com.au> writes:

> It strikes me that there are really two types of query hint possible here.
>
> One tells the planner (eg) "prefer a merge join here".
>
> The other gives the planner more information that it might not otherwise
> have to work with, so it can improve its decisions. "The values used in
> this join condition are highly correlated".

This sounds familiar:

http://article.gmane.org/gmane.comp.db.postgresql.devel.general/55730/match=hints

Plus ça change...

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's On-Demand Production Tuning

pgsql-performance by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
Next
From: Greg Smith
Date:
Subject: Re: Filesystem benchmarking for pg 8.3.3 server