"Sergey E. Koposov" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
