Sure! It give the right information to solve the problem. But as I said: On Fri, Oct 28, 2011 at 07:11, Robert Young <yay...@gmail.com> wrote: > 2.hard-coding is NOT configurable, that is the problem must be aided > from OUTSIDE of the system to workaround. >
On Wed, Nov 9, 2011 at 16:48, Bruce Momjian <br...@momjian.us> wrote: > Robert Young wrote: >> 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 > > Well, that's about as good as we can reasonably do. > > -- > 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