| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: pg_migrator and an 8.3-compatible tsvector data type |
| Date: | 2009-05-28 21:44:32 |
| Message-ID: | 4A1F05C0.6090006@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce,
> The ordering of the lexems was changed:
>
> /*
> * Convert 8.3 tsvector to 8.4
> *
> * 8.3 sorts lexemes by its length and if lengths are the same then it uses
> * alphabetic order; 8.4 sorts lexemes in lexicographical order, e.g.
> *
> * => SELECT 'c bb aaa'::tsvector;
> * tsvector
> * ----------------
> * 'aaa' 'bb' 'c' -- 8.4
> * 'c' 'bb' 'aaa' -- 8.3
> */
What does that get us in terms of performance etc.?
Given that it's going to prevent users of Tsearch from
upgrading-in-place, the format change ought to be giving us some serious
gains. Otherwise we should put it off until we need to make other
datatype changes.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-05-28 21:46:22 | Re: pg_migrator and an 8.3-compatible tsvector data type |
| Previous Message | Bruce Momjian | 2009-05-28 21:42:27 | Re: pg_migrator and an 8.3-compatible tsvector data type |