"luigisag@gmail.com" <luigisag@gmail.com> wrote:=0A=0A>=A0=A0=A0=A0=A0=A0=
=A0=A0 CREATE TABLE "User_Full_Text_Search_2" (=0A>=A0=A0=A0=A0=A0=A0=A0=A0=
"Email" varchar(50),=0A>=A0=A0=A0=A0=A0=A0=A0=A0 "UserId" varchar(50),=0A>=
=A0=A0=A0=A0=A0=A0=A0=A0 "Full_Text_Search" varchar(4096),=0A>=A0=A0=A0=A0=
=A0=A0=A0=A0 "tsv" varchar(4096)=0A>=A0=A0=A0=A0=A0=A0=A0=A0 )=0A>=A0=A0=A0=
=A0=A0=A0=A0=A0 WITH (OIDS=3DFALSE)=0A>=A0=A0=A0=A0=A0=A0=A0=A0 ;=0A=0A>=A0=
=A0=A0=A0=A0=A0=A0=A0 CREATE INDEX IX_FullText_2 ON "User_Full_Text_Search_=
2"=0A>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 USING gin("tsv");=0A=0A> I don't under=
stand why a materialized column is more slow than a=0A> calculeted one...=
=0A=0ATry materializing it as a tsvector instead of a varchar.=0A=0A--=0AKe=
vin Grittner=0AEnterpriseDB: http://www.enterprisedb.com=0AThe Enterprise P=
ostgreSQL Company