From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: [COMMITTERS] pgsql: Temporarily modify tsearch regression tests to suppress notice |
Date: | 2007-09-29 14:50:34 |
Message-ID: | 3377.1191077434@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> 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)?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-29 15:50:07 | pgsql: Defend against openssl libraries that fail on keys longer than |
Previous Message | User Eggyknap | 2007-09-29 13:51:46 | pllolcode - pllolcode: Add TODO list, with one entry RE: TOAST'd types. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-29 15:01:33 | Re: Something's been bugging me |
Previous Message | Tom Lane | 2007-09-29 14:41:55 | Re: PGBuildfarm member skylark Branch HEAD Failed at Stage Make |
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2007-09-29 15:33:46 | Re: pgcrypto: fix for broken solaris openssl, v03 |
Previous Message | Tom Lane | 2007-09-29 14:45:06 | Re: OpenSSL Applink |