Re: `inet` docs suggestion and possible bug report

Sounds good. Thanks for researching this! On Tue, Apr 29, 2025, 4:37 PM Tom Lane wrote: > I wrote: > > Nathan Long writes: > >> At least in the case of `inet`, another reason is for accurate > comparison. > >> IPv4 and IPv6 both have shorthand textual representations; eg `127.1` = > >> `127.1.0

Re: `inet` docs suggestion and possible bug report

I wrote: > Nathan Long writes: >> At least in the case of `inet`, another reason is for accurate comparison. >> IPv4 and IPv6 both have shorthand textual representations; eg `127.1` = >> `127.1.0.0`. Text storage would consider these unequal. > I'm not sure how much we want to press that point, b

Re: `inet` docs suggestion and possible bug report

Nathan Long writes: > At least in the case of `inet`, another reason is for accurate comparison. > IPv4 and IPv6 both have shorthand textual representations; eg `127.1` = > `127.1.0.0`. Text storage would consider these unequal. I'm not sure how much we want to press that point, because AFAICS th

`inet` docs suggestion and possible bug report

On https://www.postgresql.org/docs/current/datatype-net-types.html the opening paragraph says: > PostgreSQL offers data types to store IPv4, IPv6, and MAC addresses, as shown in Table 8.21 . It is better to u