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

From Jesper Krogh
Subject Re: Planner selects different execution plans depending on limit
Date
Msg-id 5051F227.7090600@krogh.cc
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
List pgsql-performance
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.

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.

Jesper


pgsql-performance by date:

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