Zoltan Boszormenyi <zb@cybertec.at> writes:
> Bruce Momjian �rta:
>> What is the use case for such a cast?
> The application doesn't want to parse the textual IP address
> when all the parsing and checking intelligence is already there
> in the inet/cidr type checks.
This presumes exactly the assumption we are questioning, namely that
there's a universal binary representation for these things. There might
be such for bare IP addresses (ignoring endianness) but the argument
doesn't scale to CIDR. You've also failed to make the case that this
application designer has made a sane judgment about whether avoiding
parsing is a good tradeoff here.
Also: to the extent that the application is willing to deal with a
Postgres-specific inet/cidr representation (which, in the end, is
what this would be) it can do that *today* using binary output format.
So I'm still not seeing an argument for exposing a cast to bytea.
regards, tom lane
