| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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 22:20:11 |
| Message-ID: | 4A1F0E1B.7060704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
> It was changed to support partial-match tsvector queries. Without it,
> a partial match query would have to scan entire tsvectors instead
> of applying binary search. I don't know if Oleg and Teodor did any
> actual performance tests on the size of the hit, but it seems like
> it could be pretty awful for large documents.
Ah, ok, that's pretty significant. It makes a huge difference for some
users, one of whom will be quoted on the press release.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-05-28 22:26:52 | Re: pg_migrator and an 8.3-compatible tsvector data type |
| Previous Message | Tom Lane | 2009-05-28 22:19:01 | Re: pg_migrator and an 8.3-compatible tsvector data type |