From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200711210458.lAL4wpN06312@momjian.us>
Subject: Re: BUG #3767: tsearch2 index creation fatal crash
In-Reply-To: <23539.1195620792@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 20 Nov 2007 23:58:51 -0500 (EST)
CC: "Thomas H." <me@alternize.com>, pgsql-bugs@postgresql.org,
	pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Tom Lane wrote:
> "Thomas H." <me@alternize.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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +