Re: IPv6 patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Nigel Kukard <nkukard(at)lbsd(dot)net>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: IPv6 patch
Date: 2003-01-07 16:17:01
Message-ID: 200301071617.h07GH1G13947@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


You mean ship with only IPv4 enabled, but not IPv6. (Of course, both
are enabled in the binary.) But then what does -i do? We currently
tell people to use -i. Do we need another postgresql.conf option that
says, "If tcpip_socket is enabled, enable IPv6 too"? But that doesn't
work if you want _only_ IPv6.

The big problem is it doesn't mix with tcpip_socket and -i very well. I
am not saying I have a better idea, I am just looking for something
clearer. Perhaps we need a separate flag/postgresql.conf option for
IPv6 so they can be controlled separately. Have we figured out how to
listen on IPv6 only?

---------------------------------------------------------------------------

Nigel Kukard wrote:
>
> IPV4 only should be shipped by default, but disabled as it is at present.
>
>
> On Tue, 7 Jan 2003, Bruce Momjian wrote:
>
> >
> > OK, what do we ship as a default?
> >
> > ---------------------------------------------------------------------------
> >
> > Nigel Kukard wrote:
> > > Sorry i'm not subscribed to hackers, guess i must get soon!
> > >
> > >
> > > Anyway what i think should happen is follows, if in the configuration file
> > > we specify that it must bind to both ie. tcpip_socket = true, the server
> > > should check if first its compiled to support ipv6 (or skip this if we use
> > > #ifdef's) and secondly bind to what WE tell it to. If we specify TRUE it
> > > must try to bind to both. Ok thats the first case, the second case is if
> > > we specify ipv4, ie. tcpip_socket = 4. This should ONLY bind ipv4, not ipv6
> > > and if there is no ipv4 support on the box it should fail, not fallback.
> > > And finally the third case, if we specify tcpip_socket = 6, we should
> > > again ONLY bind to ipv6, if there is no ipv6 support compiled, or if we
> > > cannot bind to the specific interface we should fail.
> > >
> > > Thats my opinion ;)
> > >
> > >
> > > -Nigel
> > >
> > >
> > >
> > > On 6 Jan 2003, Robert Treat wrote:
> > >
> > > > On Mon, 2003-01-06 at 16:40, Bruce Momjian wrote:
> > > > > Peter Eisentraut wrote:
> > > > > > Bruce Momjian writes:
> > > > > The issue is that right now, there isn't any special IPv6 enabling,
> > > > > except for lines in pg_hba.conf. I think it is fine to add some
> > > > > enabling, but we then have an additional user interface issue. One idea
> > > > > I had was to change tcpip_socket from true/false to true/false/4/6 so
> > > > > you can specify if you want none(false)/4/6/both(true). The original
> > > > > patch author wants this functionality too, so there clearly is a need
> > > > > for this. This doesn't play nice with the -i flag, however.
> > > > >
> > > >
> > > > Would there a downside to specifying both (enabling ipv6) on a machine
> > > > that doesn't support it? If not I'd suggest making -i equivalent to
> > > > tcp_ip_socket = true. I don't think it's too much to ask people to use
> > > > the preferred method to obtain maximum functionality.
> > > >
> > > > > Also, keep in mine my BSD/OS has libraries to support IPv6, but IPv6
> > > > > isn't enabled in the kernel, so there is a case where HAVE_IPV6 is true,
> > > > > but when run, opening an IPV6 server fails and I fall back to IPv4 ---
> > > > > just throwing that out as a data point. What would be our default as
> > > > > shipped?
> > > >
> > > > If there is no downside to allowing both, probably both. If there is a
> > > > downside then ipv4, since it much more likely to be the default on OS's
> > > > for the next release or two.
> > > >
> > > > Robert Treat
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > >
> > >
> > > Nigel Kukard (Chief Executive Officer)
> > > Lando Technologies Africa (Pty) Ltd
> > > nigel(at)lando(dot)co(dot)za www.lando.co.za
> > > Tel: 083 399 5822 Fax: 086 1100036
> > > Hoheisen Park Bellville, Cape Town
> > > National Internet Service Provider
> > >
> > >
> > > The best language to use is the language that was designed for
> > > what you want to use it for - 1997
> > >
> > >
> > > =====================================================================
> > >
> > > Disclaimer
> > > ----------
> > > The contents of this message and any attachments are intended
> > > solely for the addressee's use and may be legally privileged and/or
> > > confidential information. This message may not be retained,
> > > distributed, copied or used if you are not he addressee of this
> > > message. If this message was sent to you in error, please notify
> > > the sender immediately by reply e-mail and then destroy the message
> > > and any copies thereof.
> > >
> > > Opinions, conclusions and other information in this message may be
> > > personal to the sender and is not that of Lando Technologies Africa
> > > or any of it's subsideries, associated companies or principals and
> > > is therefore not endorsed by any of the Lando groups of companies.
> > > Due to e-maill communication being insecure, Lando groups of
> > > companies do not guarantee confidentiality, security, accuracy or
> > > performance of the e-mail. Any liability for viruses is excluded
> > > to the fullest extent.
> > >
> > >
> >
> >
>
> --
>
>
> Nigel Kukard (Chief Executive Officer)
> Lando Technologies Africa (Pty) Ltd
> nigel(at)lando(dot)co(dot)za www.lando.co.za
> Tel: 083 399 5822 Fax: 086 1100036
> Hoheisen Park Bellville, Cape Town
> National Internet Service Provider
>
>
> The best language to use is the language that was designed for
> what you want to use it for - 1997
>
>
> =====================================================================
>
> Disclaimer
> ----------
> The contents of this message and any attachments are intended
> solely for the addressee's use and may be legally privileged and/or
> confidential information. This message may not be retained,
> distributed, copied or used if you are not he addressee of this
> message. If this message was sent to you in error, please notify
> the sender immediately by reply e-mail and then destroy the message
> and any copies thereof.
>
> Opinions, conclusions and other information in this message may be
> personal to the sender and is not that of Lando Technologies Africa
> or any of it's subsideries, associated companies or principals and
> is therefore not endorsed by any of the Lando groups of companies.
> Due to e-maill communication being insecure, Lando groups of
> companies do not guarantee confidentiality, security, accuracy or
> performance of the e-mail. Any liability for viruses is excluded
> to the fullest extent.
>
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rocco Altier 2003-01-07 16:35:20 Re: IPv6 patch
Previous Message Lee Kindness 2003-01-07 16:12:26 Re: PostgreSQL libraries - PThread Support, but not use...