Re: Summary: what to do about INET/CIDR - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Summary: what to do about INET/CIDR
Date
Msg-id 29394.973392362@sss.pgh.pa.us
Whole thread Raw
In response to Re: Summary: what to do about INET/CIDR  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Summary: what to do about INET/CIDR  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> A separate function for formatting output seems necessary, but if we don't
> reach an agreement though, it ought to work to cast CIDR to INET to get
> all four octets, no?

Uh, weren't you one of the people objecting to relying on cidr-to-inet
casts to control formatting?

> I think the typecast-to-text representation of CIDR should be visually the
> same as the normal representation.

Well, we need *some* way to extract a representation like "w.x.y.z/n".
If you don't like text() as the name of that formatting function,
suggest another name...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Summary: what to do about INET/CIDR
Next
From: Bruce Momjian
Date:
Subject: Thoughts on 7.0.3 pg_dump addition