BUG #18549: Support ipv6 link-local addresses in the inet type

Started by PG Bug reporting formover 1 year ago3 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following bug has been logged on the website:

Bug reference: 18549
Logged by: Johannes Ernst
Email address: git@j12t.org
PostgreSQL version: 16.1
Operating system: All
Description:

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

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: PG Bug reporting form (#1)
Re: BUG #18549: Support ipv6 link-local addresses in the inet type

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

#3Johannes Ernst
git@j12t.org
In reply to: Tom Lane (#2)
Re: BUG #18549: Support ipv6 link-local addresses in the inet type

Currently, this causes a crash in Mastodon as it attempts to store the source of an incoming HTTP request. Which isn't very nice.

It's not clear to me that Mastodon is the place where this string should be dealt with. Simply store it as uninterpreted string if that's what it is?