| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <robertmhaas(at)gmail(dot)com>,<tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>,<sfrost(at)snowman(dot)net> |
| Subject: | Re: ANALYZE versus expression indexes with nondefault opckeytype |
| Date: | 2010-08-01 15:34:37 |
| Message-ID: | 4C554DC30200002500033FC2@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
Robert Haas writes:
>> I guess I'd appreciate it if someone could explain in more detail
>> in what cases we fail to collect stats.
> [detailed description]
> I don't think this can be claimed to be a corner case. If you set
> up an FTS index according to the first alternative offered in
>
>
http://developer.postgresql.org/pgdocs/postgres/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX
>
> you will find that the system fails to collect stats for it and so
> you get stupid default estimates for your FTS queries.
Objection to a fix in 9.0 withdrawn. No opinion on backpatching.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-01 15:35:34 | Re: review: psql: edit function, show function commands patch |
| Previous Message | Pavel Stehule | 2010-08-01 15:22:37 | Re: review: psql: edit function, show function commands patch |