| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: could not create IPv6 socket (AI_ADDRCONFIG) |
| Date: | 2014-02-04 13:30:34 |
| Message-ID: | 20140204133034.GM10723@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> > Hello, I have often seen inquiries about an log message from
> > PostgreSQL server.
> >> LOG: could not create IPv6 socket: Address family not supported by protocol
>
> That's merely a harmless log message.
> If we're concerned about users worrying about log messages from
> this, I'd rather see us downgrade those log messages to DEBUG level
> than risk breaking the code with behaviors that were proven to be
> a bad idea a decade ago. But TBH I see no strong need to do anything
> here.
How about just adding a HINT?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-04 15:31:03 | Re: could not create IPv6 socket (AI_ADDRCONFIG) |
| Previous Message | Andres Freund | 2014-02-04 12:58:23 | specifying repeatable read in PGOPTIONS |