| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | "luigisag(at)gmail(dot)com" <luigisag(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #8048: Text Search |
| Date: | 2013-04-09 15:20:10 |
| Message-ID: | 1365520810.78470.YahooMailNeo@web162906.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"luigisag(at)gmail(dot)com" <luigisag(at)gmail(dot)com> wrote:
> CREATE TABLE "User_Full_Text_Search_2" (
> "Email" varchar(50),
> "UserId" varchar(50),
> "Full_Text_Search" varchar(4096),
> "tsv" varchar(4096)
> )
> WITH (OIDS=FALSE)
> ;
> CREATE INDEX IX_FullText_2 ON "User_Full_Text_Search_2"
> USING gin("tsv");
> I don't understand why a materialized column is more slow than a
> calculeted one...
Try materializing it as a tsvector instead of a varchar.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-04-09 15:23:59 | Re: BUG #8048: Text Search |
| Previous Message | th | 2013-04-09 15:01:33 | BUG #8049: Incorrect results when using ORDER BY and query planner options |