Re: Brokenness in parsing of pg_hba.conf - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Brokenness in parsing of pg_hba.conf
Date
Msg-id 3FFC56EE.2020702@dunslane.net
Whole thread Raw
In response to Re: Brokenness in parsing of pg_hba.conf  (Kurt Roeckx <Q@ping.be>)
Responses Re: Brokenness in parsing of pg_hba.conf
Re: Brokenness in parsing of pg_hba.conf
List pgsql-hackers
Kurt Roeckx wrote:

>For getaddrinfo() it says:
>
>     If the nodename argument is not null, it can be a descriptive name
>     or can be an address string. If the specified address family is
>     AF_INET, [IP6] [Option Start]  AF_INET6, [Option End] or AF_UNSPEC,
>     valid descriptive names include host names. If the specified
>     address family is AF_INET or AF_UNSPEC, address strings using
>     Internet standard dot notation as specified in inet_addr() are
>     valid.
>
>     [IP6] [Option Start] If the specified address family is AF_INET6 or
>     AF_UNSPEC, standard IPv6 text forms described in inet_ntop() are
>     valid. [Option End]
>
>
>I'm not sure what this really says, but I can read it to either
>use the inet_addr() or inet_ntop() behaviour.
>
>
>  
>

I read it to mean that abbreviated forms (via inet_addr()) are OK for 
AF_INET but not for AF_INET6 (via inet_pton())

Does anyone else read it differently?

cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in new buffer freelist code
Next
From: "Dann Corbit"
Date:
Subject: Dumb question: How do I determine programmatically if a column is nullable?