Re: IPv6 Support for INET/CIDR types. - Mailing list pgsql-patches
| From | Larry Rosenman |
|---|---|
| Subject | Re: IPv6 Support for INET/CIDR types. |
| Date | |
| Msg-id | 20020222201701.GA15416@lerami.lerctr.org Whole thread Raw |
| In response to | Re: IPv6 Support for INET/CIDR types. (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Responses |
Re: IPv6 Support for INET/CIDR types.
|
| List | pgsql-patches |
* Bruce Momjian <pgman@candle.pha.pa.us> [020222 13:56]:
>
> OK, I have forwarded my saved emails to Paul. Paul, there was great
> confusion over how these data types show display addresses and masks,
> and a compromise was hammered out that we are reluctant to throw out.
>
> I wish our email archives where searchable online and I could point you
> to the issues. Can someone summarize the issues, specifically how did
> we change what Paul originally gave us so it can be done again? All I
> have for detail is this from Tom Lane:
>
> The patch as given reverts the I/O behavior of the inet datatypes
> to what it originally was, rather than the compromise behavior that
> was hammered out at great length before 7.1. (I'd give a link to
> those discussions if fts.postgresql.org were working :-()
>
> Seems the archives were down back then in October too. :-(
Please do *NOT* revert the output functions. One of the MAJOR reasons
for the change was to ALWAYS print ALL 4 octets of an IPv4 address in
the default case.
You (Paul) were part of that discussion. I was one of the instigators
of it.
LER
>
>
> ---------------------------------------------------------------------------
>
> Paul Vixie wrote:
> > here's the problem. i want to replace the inet_{net_}{ntop,pton}
> > functions in postgres with the real ones from bind. however, your
> > versions have been patched. so before i can replace them i need
> > to understand exactly what you've patched and move that logic to
> > the part of postgres that calls these functions. then i can import
> > the real versions, which include vadim's ipv6 logic. then i can
> > work on changing postgres to use the new ipv6 logic in these functions.
> >
> > any help with that first step would be appreciated.
> >
> > > From: Bruce Momjian <pgman@candle.pha.pa.us>
> > > Message-Id: <200202221810.g1MIA6C29715@candle.pha.pa.us>
> > > Subject: Re: [PATCHES] IPv6 Support for INET/CIDR types.
> > > In-Reply-To: <200110161420.f9GEKZH87408@as.vix.com>
> > > To: Paul A Vixie <paul@vix.com>
> > > Date: Fri, 22 Feb 2002 13:10:06 -0500 (EST)
> > > Cc: "Marc G. Fournier" <scrappy@hub.org>,
> > > Vadim Kogan <vadim@xcf.berkeley.edu>, pgsql-patches@postgresql.org
> > > X-Mailer: ELM [version 2.4ME+ PL96 (25)]
> > > MIME-Version: 1.0
> > > Content-Transfer-Encoding: 7bit
> > > Content-Type: text/plain; charset=US-ASCII
> > >
> > > Paul A Vixie wrote:
> > > > > > Seems this will have to wait for 7.3.
> > > > >
> > > > > Why?
> > > >
> > > > because i didn't get it fixed in time.
> > > >
> > > > > and, to be a bit more riendly to those of us stuck on 56k lines, could you
> > > > > avoid re-sending, repeatedly, large patch files?
> > > >
> > > > sorry.
> > >
> > > Paul, do you have an updated patch that can be applied to 7.3?
> > >
> > > --
> > > Bruce Momjian | http://candle.pha.pa.us
> > > pgman@candle.pha.pa.us | (610) 853-3000
> > > + If your life is a hard drive, | 830 Blythe Avenue
> > > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
> >
> >
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
pgsql-patches by date: