Re: Weirdness with the stats collector process

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthew Musgrove <mmusgrove(at)emortgagelogic(dot)com>
Cc: "Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>; Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Weirdness with the stats collector process
Date: 2016-07-26 19:59:15
Message-ID: 8731.1469563155@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Matthew Musgrove <mmusgrove(at)emortgagelogic(dot)com> writes:
> I asked what network changes were made on July 7th around 14:05 and was told that they disabled IPv6! I had them turn it back on and stats started working immediately.

Ooops ...

> I have since changed the config from listen_addresses = '*' to listen_addresses = '0.0.0.0' but we won't be restarting until our next maintenance window (in about a week) when they will disable IPv6 again.

AFAIR, listen_addresses doesn't have any impact on our choice of stats
collector loopback port: we just look up "localhost" at postmaster start,
and use whatever that resolves as. It's fairly common these days for that
to resolve as both "::1" and "127.0.0.1", and we'll use whichever of those
is first found to work. So this change would probably have been fine if
it were made when PG wasn't running, but it was pretty foolish to do it to
a running system without even looking to see if any IPV6 connections were
open :-(

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-07-26 20:29:17 Re: yum repo, pgloader
Previous Message John R Pierce 2016-07-26 19:54:59 Re: yum repo, pgloader