From: | Andy Colson <andy(at)squeakycode(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: cannot get stable function to use index |
Date: | 2015-12-30 21:16:41 |
Message-ID: | 568449B9.9050306@squeakycode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/30/2015 2:39 PM, Andy Colson wrote:
> On 12/30/2015 2:33 PM, Tom Lane wrote:
>> Andy Colson <andy(at)squeakycode(dot)net> writes:
>>> On 12/30/2015 2:18 PM, Tom Lane wrote:
>>>> Maybe something weird about the build you're using? What does
>>>> pg_config print?
>>
>>> [ output ]
>>
>> No smoking gun there either.
>>
>> It might be worthwhile to update to 9.3.10, just in case there is
>> something wonky about this particular build you've got. But I'm
>> starting to get the feeling that you may not get an answer short
>> of tracing through gincostestimate to see where it's going nuts.
>>
>> regards, tom lane
>>
>
> The entire database is 78Gig, would you expect a "vacuum analyze" to fix
> it? I never run it.
>
Ok, I can reproduce this now. The full vacuum analyze isn't needed.
If I drop and recreate the table it goes back to preferring table scan.
I can "analyze search" and it still table scans.
But once I "vacuum analyze search", then it starts index scanning.
-Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-30 22:58:42 | Re: cannot get stable function to use index |
Previous Message | Andy Colson | 2015-12-30 20:39:30 | Re: cannot get stable function to use index |