| From: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org>, pgsql-admin(at)postgresql(dot)org, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: postgres started without auto vaccum |
| Date: | 2018-02-16 17:21:36 |
| Message-ID: | CAKUuFd6SLNEs=2WaruntPwkQNDFLkEFAWg1mY5J8N=ifGdHXyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Yes, I did. The first start happened without any issues. But the next
restart i see the errors.
On Feb 16, 2018 7:54 AM, "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 02/15/2018 09:54 PM, Azimuddin Mohammed wrote:
>
>> Hello All,
>> I am getting below Warning messages in logs after starting postgres, can
>> some please help me here
>>
>> LOG: could not bind socket for statistics collector: Cannot assign
>> requested address
>>
>> LOG: disabling statistics collector for lack of working socket
>>
>> WARNING: autovacuum not started because of misconfiguration
>>
>> HINT : Enable the "track_counts" option.
>>
>> MultiXact member wraparound protections are now enabled
>>
>>
>> I tried enabling track_counts but it did not help.
>>
>
> Did you restart the server after making the change?
>
> Did Postgres start without the warnings previous to this?
>
>
>>
>> Any guidance is much appreciated here.
>>
>>
>> Thanks in Advance!
>>
>>
>>
>> --
>>
>> Regards,
>> Azim
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2018-02-16 17:37:25 | Re: postgres started without auto vaccum |
| Previous Message | Adrian Klaver | 2018-02-16 13:54:14 | Re: postgres started without auto vaccum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2018-02-16 17:37:25 | Re: postgres started without auto vaccum |
| Previous Message | Thomas Kellerer | 2018-02-16 16:42:27 | Re: Database health check/auditing |