From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GIN indexscans versus equality selectivity estimation |
Date: | 2011-01-11 01:09:19 |
Message-ID: | 3768.1294708159@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> On 1/10/11 7:25 AM, Tom Lane wrote:
>> I'm a bit worried though that there might be other
>> cases where the estimator comes up with 1.0 selectivity but it'd still
>> be worth considering a bitmap scan.
> Well, I think the answer is to apply the other fixes, and test. If
> there are other cases of selectivity=1.0, they'll show up. People are
> pretty fast to complain if indexes aren't used, and we have a good
> production test case available once you implement the other operators.
"Implement the other operators"? I don't think we're on the same page
here. What I'm talking about is a one-line change in indxpath.c to not
short-circuit consideration of a bitmap indexscan.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-01-11 01:13:47 | Re: Weird issues when reading UDT from stored function |
Previous Message | Tom Lane | 2011-01-11 01:04:19 | Re: Compatibility GUC for serializable |