Re: -HEAD planner issue wrt hash_joins on dbt3 ?

From: Matteo Beccati <php(at)beccati(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: -HEAD planner issue wrt hash_joins on dbt3 ?
Date: 2006-09-18 15:46:24
Message-ID: 450EBF50.7050402@beccati.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane ha scritto:
> Matteo Beccati <php(at)beccati(dot)com> writes:
>> I cannot see anything bad by using something like that:
>> if (histogram is large/representative enough)
>
> Well, the question is exactly what is "large enough"? I feel a bit
> uncomfortable about applying the idea to a histogram with only 10
> entries (especially if we ignore two of 'em). With 100 or more,
> it sounds all right. What's the breakpoint?

Yes, I think 100-200 could be a good breakpoint. I don't actually know
what is the current usage of SET STATISTICS, I usually set it to 1000
for columns which need more precise selectivity.

The breakpoint could be set even higher (500?) so there is space to
increase statistics without enabling the histogram check, but I don't
feel very comfortable though suggesting this kind of possibly
undocumented side effect...

Best ragards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-09-18 15:52:17 Re: 8.2 beta blockers
Previous Message Tom Lane 2006-09-18 15:35:11 Re: [PATCHES] Linking on AIX (Was: Fix linking of OpenLDAP libraries )