Re: Installing Postgresql on Linux Friendlyarm - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Installing Postgresql on Linux Friendlyarm
Date
Msg-id 54241F68.8060003@aklaver.com
Whole thread Raw
In response to Re: Installing Postgresql on Linux Friendlyarm  (Xiang Gan <XiangGan@santaitech.com>)
List pgsql-general
On 09/24/2014 11:34 PM, Xiang Gan wrote:
> Finally, I managed to run Postgresql in Linux FriendlyARM environment. It seems that Postgresql server starts to
work,however, it prints out some WARNING info. during the start. The error info. is as follows: 
>
> LOG: could not resolve "localhost": Temporary failure in name resolution
> LOG: disabling statistics collector for lack of working socket
> WARNING: autovacuum not started because of misconfiguration
> HINT: Enable the "track_counts" option.
>
>
> So the above log indicates that autovacuum failed to start mainly due to the problem that "localhost" cannot be
resolvedas 127.0.0.1? But I can ping localhost from command line without any problem. My /etc/hosts file reads as: 
> 127.0.0.1 localhost.localdomain localhost
>
> In addition, options "autovacuum" and "track_counts" are turned on by default in postgresql.conf file. But in
database,with command "show autovacuum", its value is shown as "on" while with command "show track_counts", its value
isshown as "off". 

There is a cascading effect. The statistics collector needs a working
socket and autovacuum needs a working statistics collector, in
particular track_counts. You fix the socket/networking issues the other
issues should resolve.

>
> Could anyone provide some hints about how to handle this kind of problem?

Well this going to depend greatly on what you did to get to this phrase
'I managed to run Postgresql in Linux FriendlyARM environment.'.

So a detailed explanation on how you got Postgres to sort of start would
be in order.

>
> Kind regards,
> Gerry
>
>
>



--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: How to clone CURRENT_DATE to SYSDATE ?
Next
From: Alvaro Herrera
Date:
Subject: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement