From: Jesper Krogh <jesper@krogh.cc>
To: Bill Martin <bill.martin@communote.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Planner selects different execution plans depending on limit
Date: Thu, 13 Sep 2012 16:48:07 +0200
Message-ID: <5051F227.7090600@krogh.cc> (raw)
In-Reply-To: <D48BF41C96B16442B542F5E25C259047011E80F02A@COM211.communardo.local>
References: <D48BF41C96B16442B542F5E25C259047011E80F02A@COM211.communardo.local>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jesper@krogh.cc, bill.martin@communote.com, tgl@sss.pgh.pa.us
Subject: Re: Planner selects different execution plans depending on limit
In-Reply-To: <5051F227.7090600@krogh.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox