| From: | Jesper Krogh <jesper(at)krogh(dot)cc> |
|---|---|
| To: | Bill Martin <bill(dot)martin(at)communote(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Planner selects different execution plans depending on limit |
| Date: | 2012-09-13 14:48:07 |
| Message-ID: | 5051F227.7090600@krogh.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-13 14:54:19 | Re: Planner selects different execution plans depending on limit |
| Previous Message | Bill Martin | 2012-09-13 14:42:07 | Re: Planner selects different execution plans depending on limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-13 14:54:19 | Re: Planner selects different execution plans depending on limit |
| Previous Message | Bill Martin | 2012-09-13 14:42:07 | Re: Planner selects different execution plans depending on limit |