Hi all<div class=""><br class="" /></div><div class="">I just ran into an issue that was originally reported way back
in2007 - <a class=""
href="https://www.postgresql.org/message-id/flat/0262B803-B664-4EBE-85B4-3C9A40EA6CDA@mobygames.com">https://www.postgresql.org/message-id/flat/0262B803-B664-4EBE-85B4-3C9A40EA6CDA@mobygames.com</a></div><div
class=""><brclass="" /></div><div class="">Basically the inet data type cannot store or parse valid ipv6 address
literalswith a scope / zone id suffix. Apparently the combination of virtualised linux, ipv6 network and JVM that we
areusing has combined to report connections on localhost as coming from ‘::1%0’, which our app is unsuccessfully
attemptingto store in the db in an inet column. This is the first time that I have ever seen this, but perhaps it will
getmore common as ipv6-first usage increases.</div><div class=""><br class="" /></div><div class="">Given that inet is
avarlena struct with only known-length fields, it seems potentially possible to extend it to add an optional, variable
lengthzone id on the end, with the result being backwards compatible with existing data.</div><div class=""><br
class=""/></div><div class="">Thoughts?</div><div class=""><br class="" /></div><div class="">Cheers</div><div
class=""><brclass="" /></div><div class="">Tom</div><div class=""><br class="" /></div>