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 26906.1347548059@sss.pgh.pa.us
Whole thread Raw
In response to Re: Planner selects different execution plans depending on limit  (Jesper Krogh <jesper@krogh.cc>)
Responses Re: Planner selects different execution plans depending on limit
List pgsql-performance
Jesper Krogh <jesper@krogh.cc> writes:
> On 13/09/12 16:42, Bill Martin wrote:
>> Yes, I've run the ANALYZE command. Regards, Bill Martin

> The main problem in your case is actually that you dont store the
> tsvector in the table.

Oh, duh, obviously I lack caffeine this morning.

> If you store to_tsvector('simple',content.content) in a column in
> the database and search against that instead
> then you'll allow PG to garther statistics on the column and make the
> query-planner act according to that.

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.

            regards, tom lane


pgsql-performance by date:

Previous
From: Jesper Krogh
Date:
Subject: Re: Planner selects different execution plans depending on limit
Next
From: Bill Martin
Date:
Subject: Re: Planner selects different execution plans depending on limit