Re: [HACKERS] [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice

2007-09-29 Thread Tom Lane
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

Re: [HACKERS] [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice

2007-09-29 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> 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

Re: [HACKERS] [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice

2007-09-27 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> 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 n

Re: [HACKERS] [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice

2007-09-26 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > I just talked to Teodor and we discussed this problem. My idea is to > > have a special marker in the synonym table, perhaps "*" to indicate the > > presence of _any_ stop word at that location. This will not produce any > > warnings

Re: [HACKERS] [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice

2007-09-26 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > I just talked to Teodor and we discussed this problem. My idea is to > have a special marker in the synonym table, perhaps "*" to indicate the > presence of _any_ stop word at that location. This will not produce any > warnings because it is clearly int