| From: | Jesper Krogh <jesper(at)krogh(dot)cc> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsvector pg_stats seems quite a bit off. |
| Date: | 2010-05-31 18:12:51 |
| Message-ID: | 4C03FC23.8000109@krogh.cc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2010-05-30 20:02, Jan Urbański wrote:
> Here's a patch against recent git, but should apply to 8.4 sources as
> well. It would be interesting to measure the memory and time needed to
> analyse the table after applying it, because we will be now using a lot
> bigger bucket size and I haven't done any performance impact testing on
> it. I updated the initial comment block in compute_tsvector_stats, but
> the prose could probably be improved.
>
Just a small follow up. I tried out the patch (or actually a fresh git
checkout) and it now gives very accurate results for both upper and
lower end of the MCE-histogram with a lower cutoff that doesn't
approach 2.
Thanks alot.
--
Jesper
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-31 18:38:19 | Re: tsvector pg_stats seems quite a bit off. |
| Previous Message | Bruce Momjian | 2010-05-31 17:05:52 | Re: 9.0b1: "ERROR: btree index keys must be ordered by attribute" |