Re: [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice
Date
Msg-id 200709291114.l8TBEPk27086@momjian.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Tom Lane wrote:
> >> That's not fixing the problem, unless your proposal includes never
> >> issuing any warnings at all, for anything.
> 
> > No warning for "*" because it is intentional, but warning for actual
> > stop words.
> 
> No, you're focusing on one symptom not the problem.  The problem is
> that we've got user-visible behavior going on during what's effectively
> a chance event, ie, a cache reload.
> 
> 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).

--  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. +


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: PGBuildfarm member skylark Branch HEAD Failed at Stage Make
Next
From: Gregory Stark
Date:
Subject: Something's been bugging me