Yes,PG told me about this: LOG: could not resolve "localhost": no address associated with name LOG: disabling statistics collector for lack of working socket WARNING: autovacuum not started because of misconfiguration HINT: Enable the "track_counts" option. LOG: database system was shut down at 2011-10-27 09:43:18 GMT LOG: database system is ready to accept connections
On Wed, Nov 9, 2011 at 15:06, Bruce Momjian <br...@momjian.us> wrote: > Andres Freund wrote: >> Hi Robert, >> >> On Thursday, October 27, 2011 12:38:02 PM Robert Young wrote: >> > What Would Happen if I got NO "localhost" entry in my /etc/hosts ? >> Why should pg cater for such a broken configuration? Sorry for being harsh >> but >> that seems like it would end in heaps of workarounds. > > Do we throw at least a log message warning if localhost isn't resolved? > If not, we should. (I don't want to break my OS to test this.) > > -- > Bruce Momjian <br...@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + It's impossible for everything to be true. + > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
