Re: What is happening on buildfarm member dugong - Mailing list pgsql-hackers

From Tom Lane
Subject Re: What is happening on buildfarm member dugong
Date
Msg-id 13756.1189530753@sss.pgh.pa.us
Whole thread Raw
In response to Re: What is happening on buildfarm member dugong  ("Sergey E. Koposov" <math@sai.msu.ru>)
Responses Re: What is happening on buildfarm member dugong
List pgsql-hackers
"Sergey E. Koposov" <math@sai.msu.ru> writes:
> On Tue, 11 Sep 2007, Tom Lane wrote:
> NOTICE:  database "contrib_regression" does not exist, skipping
> ERROR:  too many active hash_seq_search scans
> ERROR:  too many active hash_seq_search scans
> ERROR:  too many active hash_seq_search scans
> ERROR:  too many active hash_seq_search scans

> With hash_seq_search ERROR, it was partially a false alarm. I've had some 
> old postgres daemon hanging around and writing that to the log. 
> Although I remember seeing that hash_seq_search message recently when 
> dealing with this bug, it does not show up in the course of standard 
> regression tests.

Yeah, it's not there on your buildfarm reports, but that's not totally
surprising.  I would expect it to start showing up after 100 failed
checkpoint attempts, which is how long it'd take the bgwriter's
hash_seq_search table to overflow ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Per-function search_path => per-function GUC settings
Next
From: "Sergey E. Koposov"
Date:
Subject: Re: What is happening on buildfarm member dugong