Sergey E. Koposov wrote:
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.
Your buildfarm member must be seriously misconfigured if you can get the
logs from different postmasters comingled. Every run gets its own
logfile in its own inst directory.
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
