Re: Planner selects different execution plans depending on limit - Mailing list pgsql-performance

From Bill Martin
Subject Re: Planner selects different execution plans depending on limit
Date
Msg-id D48BF41C96B16442B542F5E25C259047011E8118EC@COM211.communardo.local
Whole thread Raw
In response to Re: Planner selects different execution plans depending on limit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Tom Lane <mailto:tgl@sss.pgh.pa.us> writes:
> Bill Martin <bill.martin@communote.com> writes:
>> Tom Lane <tgl@sss.pgh.pa.us> writes:
>>> He can do it without having to change his schema --- but it's the 
>>> index column, not the underlying content column, that needs its 
>>> statistics target adjusted.

>> How can I adjust the statistics target of the index?

> Just pretend it's a table.

>    ALTER TABLE index_name ALTER COLUMN column_name SET STATISTICS ...

> You'll need to look at the index (eg with \d) to see what the name of the desired column is, since index expressions
havesystem-assigned
 
> column names.

>        regards, tom lane

I tried: 
ALTER TABLE ft_simple_core_content_content_idx ALTER column to_tsvector SET STATISTICS 10000;
ANALYZE;

and
REINDEX INDEX ft_simple_core_content_content_idx;

All the trouble was for nothing.

Are there any other possibilities to solve my problem?

Best regards,
Bill Martin

pgsql-performance by date:

Previous
From: "McKinzie, Alan (Alan)"
Date:
Subject: Re: Are there known performance issues with defining all Foreign Keys as deferrable initially immediate
Next
From: Andrea Suisani
Date:
Subject: Re: 20% performance drop on PostgreSQL 9.2 from kernel 3.5.3 to 3.6-rc5 on AMD chipsets