Re: Forcing seq_scan off for large table joined with tiny table yeilds improved performance

On Mon, Apr 6, 2009 at 6:20 AM, Mario Splivalo
<mario.splivalo@megafon.hr> wrote:
> Scott Marlowe wrote:
>>
>> It's not really solved, it's just a happy coincidence that the current
>> plan runs well.  In order to keep the query planner making good
>> choices you need to increase stats target for the field in the index
>> above.  The easiest way to do so is to do this:
>>
>> alter database mydb set default_statistics_target=100;
>>
>> and run analyze again:
>>
>> analyze;
>
> So, i removed the index on field_name, set default_default_statistics_target
> to 100, analyzed, and the results are the same:

Why did you remove the index?