From: | Kurt Roeckx <Q(at)ping(dot)be> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Brokenness in parsing of pg_hba.conf |
Date: | 2004-01-07 18:25:59 |
Message-ID: | 20040107182559.GA24933@ping.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 07, 2004 at 12:53:19PM -0500, Bruce Momjian wrote:
> Greg Stark wrote:
> > a.b.c
> >
> > When a three-part address is specified, the last part shall be interpreted
> > as a 16-bit quantity and placed in the rightmost two bytes of the network
> > address. This makes the three-part address format convenient for specifying
> > Class B network addresses as "128.net.host" .
>
> I can understand the a.b case, but the a.b.c case is just weird. What
> logic is there that it is a.0.b.c? Nothing I can think of except
> convention. I agree with Vixie that this syntax is strange and
> shouldn't be encouraged.
It's a.b.0.c.
Note that the "c" can be bigger than 255, so 128.1.512 turns into
128.1.2.0. This can make perfect sense when you still used
classes.
Kurt
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-01-07 18:28:17 | Re: Brokenness in parsing of pg_hba.conf |
Previous Message | Tom Lane | 2004-01-07 18:09:20 | Re: Bug in new buffer freelist code |