Re: test failure on latest source

On 13/04/2014 18:09, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
>> On 2014-04-12 16:35:48 -0400, Tom Lane wrote:
>>> In principle, that commit shouldn't have affected behavior for pg_hba
>>> entries with numeric address fields ...
>
>> Hm. getaddrinfo.c has this bit:
>>     /* Unsupported flags. */
>>     if (flags & NI_NAMEREQD)
>>         return EAI_AGAIN;
>
> Yeah, and that flag is only ever specified when attempting to do reverse
> lookup on a client address to see if it matches a non-numeric pg_hba
> entry.
>
>             regards, tom lane
>


just to recap, as I think no one have yet proposed/implemented
a solution.

first failure I see on cygwin is from
-------------------------------------
$ git log |head
commit fc752505a99a4e2c781a070d3d42a25289c22e3c
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Wed Apr 2 17:11:24 2014 -0400
    Fix assorted issues in client host name lookup.
[cut]
-------------------------------------------

previous one is fine
------------------------------------------
commit f33a71a7865a1dd54f04b370e2637f88665f8db8
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Wed Apr 2 14:30:08 2014 -0400
    De-anonymize the union in JsonbValue.
    Needed for strict C89 compliance.
--------------------------------------------

error log
--------------------------------------------
cat 
/pub/devel/postgresql/prova/build_orig/src/test/regress/log/postmaster.log
LOG:  could not resolve "localhost": Non-recoverable 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.
LOG:  invalid IP address "127.0.0.1": Non-recoverable failure in name 
resolution
CONTEXT:  line 86 of configuration file 
"/pub/devel/postgresql/prova/build_orig/src/test/regress/./tmp_check/data/pg_hba.conf"
FATAL:  could not load pg_hba.conf
-----------------------------------------------

and of course localhost and 127.0.0.1 are valid
 $ ping localhost

Pinging GE-MATZERI-EU [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
[cut]
 $ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128