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

From Tom Lane
Subject Re: Planner selects different execution plans depending on limit
Date
Msg-id 16905.1347557599@sss.pgh.pa.us
Whole thread Raw
In response to Re: Planner selects different execution plans depending on limit  (Bill Martin <bill.martin@communote.com>)
Responses Re: Planner selects different execution plans depending on limit  (Bill Martin <bill.martin@communote.com>)
List pgsql-performance
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 have system-assigned
column names.

            regards, tom lane


pgsql-performance by date:

Previous
From: Bill Martin
Date:
Subject: Re: Planner selects different execution plans depending on limit
Next
From: Ross Reedstrom
Date:
Subject: AppScale backend datastore (NoSQL again kind of)