Bruce Momjian wrote: > Tom Lane wrote: > > Bruce Momjian <[EMAIL PROTECTED]> writes: > > > Tom Lane wrote: > > >> One possible real solution would be to tweak the dictionary APIs so > > >> that the dictionaries can find out whether this is the first load during > > >> a session, or a reload, and emit notices only in the first case. > > > > > Yea, that would work too. Or just throw an error for a stop word in the > > > file and then you never get a reload (use "*" instead). > > > > Hm, that's a thought --- it'd be a way to solve the problem without an > > API change for dictionaries, which is something to avoid at this late > > stage of the 8.3 cycle. Come to think of it, does the ts_cache stuff > > work properly when an error is thrown in dictionary load (ie, is the > > cache entry left in a sane state)? > > I have developed the attached patch which uses "?" to mark stop words in > the thesaurus file. ("*" was already in use in the file.) I updated > the docs to use "?", which makes the documentation clearer too. > > The patch also reenables testing of stop words in the thesuarus file. > > FYI, there is no longer a NOTICE for stop words in the thesaurus file; > it throws an error now, and says to use "?" instead.
Patch applied. I added documentation on this API change too. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org