Skip site navigation (1) Skip section navigation (2)

occasional startup failures

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: occasional startup failures
Date: 2012-03-25 16:12:33
Message-ID: 4F6F43F1.4050402@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Every so often buildfarm animals (nightjar and raven recently, for 
example) report failures on starting up the postmaster. It appears that 
these failures are due to the postmaster not creating the pid file 
within 5 seconds, and so the logic in commit 
0bae3bc9be4a025df089f0a0c2f547fa538a97bc kicks in. Unfortunately, when 
this happens the postmaster has in fact sometimes started up, and the 
end result is that subsequent buildfarm runs will fail when they detect 
that there is already a postmaster listening on the port, and without 
manual intervention to kill the "rogue" postmaster this continues endlessly.

I can probably add some logic to the buildfarm script to try to detect 
this condition and kill an errant postmaster so subsequent runs don't 
get affected, but that seems to be avoiding a problem rather than fixing 
it. I'm not sure what we can do to improve it otherwise, though.

Thoughts?

cheers

andrew

Responses

pgsql-hackers by date

Next:From: Billy EarneyDate: 2012-03-25 16:13:54
Subject: Re: query cache
Previous:From: Tom LaneDate: 2012-03-25 15:59:22
Subject: Re: [PATCH] Never convert n_distinct < 2 values to a ratio when computing stats

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group