On 2014-03-03 16:28:21 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > Since we have seen this kind of failure reported many times, I wonder if
> > it'd make sense to check specifically for inability to resolve localhost,
> > if only to save troubleshooters' time.
>
> Right now, you only get a failure of the pgstats subsystem, which is
> logged. I don't think we can do much more than that unless you want
> to make it a postmaster-refuses-to-start case, which seems like not
> a net improvement.
I'd actually say that'd be an improvement. I've, a long time ago, spent
several hours debugging a case of this, it's nontrivial for a
beginner. And a normal PG install simply won't work properly without
pgstat these days, so refusing to startup seems reasonable.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
