From: Tom Lane <tgl@sss.pgh.pa.us>
To: git@j12t.org
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18549: Support ipv6 link-local addresses in the inet type
In-reply-to: <18549-adf203ad53c1dae3@postgresql.org>
References: <18549-adf203ad53c1dae3@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 22 Jul 2024 16:07:56 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <895683.1721666217.1@sss.pgh.pa.us>
Date: Mon, 22 Jul 2024 12:36:57 -0400
Message-ID: <895684.1721666217@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/895684.1721666217%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> One of the variations of ipv6 addresses is link-local addresses. It would be
> nice if they could be stored in an inet column.

> Example: fe80::249a:57ff:fed6:695f%host0/128 . Note the %host0

This has been discussed in the past.  One problem is that there is no
cross-platform standardization of what the name following % can be.
So we couldn't do much better than accepting it on faith and storing
it as a string, which is not very nice.  It's also very unclear how
such a marker should affect the semantics of inet operators and
functions.

Maybe someday somebody will get motivated to try to surmount those
problems, but don't hold your breath.

			regards, tom lane