From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Thomas H(dot)" <me(at)alternize(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: BUG #3767: tsearch2 index creation fatal crash |
Date: | 2007-11-21 04:58:51 |
Message-ID: | 200711210458.lAL4wpN06312@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
Tom Lane wrote:
> "Thomas H." <me(at)alternize(dot)com> writes:
> > i saw my mistake. i misinterpreted the examples to show the possibility
> > to convert *any* text by using casting to tsvector as an alternative to
> > using to_tsvector :)
>
> Yeah, the examples in section 12.1.2 are not actually good practice:
> both sides of the match should usually get normalized before comparison,
> and these examples don't do that.
>
> I'm not sure that putting in to_tsvector calls there would be an
> improvement, though, since at that point we haven't introduced
> to_tsvector.
>
> Thoughts anyone?
Yep, I saw that chicken and egg problem in the docs when I was reviewing
it long ago. I never came up with a solution either. We would have to
introduce configurations a lot earlier, but how would you explain them
when you don't know what a tsvector is.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-21 05:04:53 | Re: BUG #3767: tsearch2 index creation fatal crash |
Previous Message | Tom Lane | 2007-11-21 04:53:12 | Re: BUG #3767: tsearch2 index creation fatal crash |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-21 05:04:53 | Re: BUG #3767: tsearch2 index creation fatal crash |
Previous Message | Tom Lane | 2007-11-21 04:53:12 | Re: BUG #3767: tsearch2 index creation fatal crash |