From: Tom Lane <tgl@sss.pgh.pa.us>
To: denis.feklushkin@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18712: inet value ::2 handling goes not as expected
In-reply-to: <18712-f787a146022a78e4@postgresql.org>
References: <18712-f787a146022a78e4@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 16 Nov 2024 06:50:10 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3065771.1731863111.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 17 Nov 2024 12:05:11 -0500
Message-ID: <3065772.1731863111@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3065772.1731863111%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I think that statement
> select '::0.0.0.2'::inet;
> should return '::0.0.0.2' value, not '::2'

> I think this is what was intended in the Postgres sources. But it seems =
that
> this line is never executed:
> https://github.com/postgres/postgres/blob/7b88529f4363994450bd4cd3c17200=
6a8a77e222/src/port/inet_net_ntop.c#L260

Hmm ... you are right that that code doesn't do what it seems to
intend to, because by the time that we get to this logic we have
i =3D=3D 7 not i =3D=3D 6.  But I'm not sure if we should change it after
all this time.  We're about as likely to get complaints as kudos,
I fear.  And the output isn't incorrect, just not-per-style.

I wonder whether ISC ever changed their version?

			regards, tom lane