From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: What is happening on buildfarm member dugong |
Date: | 2007-09-16 18:41:31 |
Message-ID: | 17371.1189968091@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> It seems to me last run
> (http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugong&dt=2007-09-11%2016:05:01)
> points to problem with hash implementation.
> SELECT to_tsvector('thesaurus_tst', 'one postgres one two one two three one');
> + NOTICE: thesaurus word-sample "the" is recognized as stop-word, assign any
> stop-word (rule 8)
> At this place of tsdicts test dictionary thesaurus should be already loaded and
> initialized, but this NOTICE points that thesaurus was initialized here.
I just realized what that probably is actually from: there was a cache
invalidation event sometime between when thesaurus was initially loaded
and when this statement tried to use it, so the ts_cache entry had to
be reloaded. The parallel regression tests are quite capable of
provoking sinval queue overflows (and ensuing cache resets) at fairly
random places.
It is not good design to have any user-visible behavior that occurs during
a cache load, because you can't predict when those will happen. Perhaps
this NOTICE should not be emitted, or should be emitted from some other
place.
(In fact, this test ought to be failing right now on whichever buildfarm
machine is supposed to be testing CLOBBER_CACHE_ALWAYS. Which animal
was that again?)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2007-09-16 18:57:22 | Re: What is happening on buildfarm member dugong |
Previous Message | Pavan Deolasee | 2007-09-16 16:36:45 | Re: Hmmm ... isn't count_nondeletable_pages all wet? |