BUG #8171: Log messages lacking enough details

From: Trond(dot)Endrestol(at)ximalas(dot)info
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #8171: Log messages lacking enough details
Date: 2013-05-20 07:32:55
Message-ID: E1UeKaV-0007AR-I2@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 8171
Logged by: Trond Endrestøl
Email address: Trond(dot)Endrestol(at)ximalas(dot)info
PostgreSQL version: 9.2.4
Operating system: FreeBSD/amd64 9.1-STABLE r250805
Description:

The log message:

LOG: could not bind IPv6 socket: Can't assign requested address

should be augmented to reveal the attempted address, thus making the lives
of us poor db admins a lot easier. Likewise for any similar IPv4 related log
messages.

In fact all kinds of log/warning/error messages should be to the point and
include all(!) relevant details and not just a vague description of what
happened.

The above log message was due to the file /etc/hosts containing the two
lines:

localhost fe80::1
localhost fe80:2::1

Changing these two lines to:

localhost-6ll fe80::1
localhost-6ll fe80:2::1

made PostgreSQL much happier.

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-05-20 13:06:18 Re: BUG #8170: alter user does not accept timestamp output format in certain datestyles and timezones.
Previous Message chris.travers 2013-05-20 04:51:41 BUG #8170: alter user does not accept timestamp output format in certain datestyles and timezones.