Re: RE: even more CIDR weirdness (was equality operator on CIDR colum n as primary key) - Mailing list pgsql-general

From Stephan Szabo
Subject Re: RE: even more CIDR weirdness (was equality operator on CIDR colum n as primary key)
Date
Msg-id Pine.BSF.4.10.10008300731250.60082-100000@megazone23.bigpanda.com
Whole thread Raw
In response to RE: even more CIDR weirdness (was equality operator on CIDR colum n as primary key)  ("Mayers, Philip J" <p.mayers@ic.ac.uk>)
List pgsql-general
IIRC, there were some problems with CIDR where it was considering
the low bits significant even though they might not have been set
(in the case of 192.169/16 for example) which was causing fairly
odd behavior.

I believe they've routed out these problems in current sources
so it should be fixed for 7.1.

Stephan Szabo
sszabo@bigpanda.com

On Wed, 30 Aug 2000, Mayers, Philip J wrote:

>
> Ok, now I'm getting truly confused. It works with some networks, but not
> with others:
>
>
> test=> select * from test;
>     network     | netcol
> ----------------+--------
>  192.168/16     | 192/8
>  192/8          | 192/4
>  155.198/16     |
>  155.198.1/24   |
>  156.198/16     |
>  156.198.1/24   |
>  193.63.75.0/27 |
> (7 rows)
>
> test=> select * from test where network = '192.168/16';
>  network | netcol
> ---------+--------
> (0 rows)
>
> test=> select * from test where network = '193.63.75.8/27';
>     network     | netcol
> ----------------+--------
>  193.63.75.0/27 |
> (1 row)
>
> test=> select * from test where network = '193.63.75.8/27';
>     network     | netcol
> ----------------+--------
>  193.63.75.0/27 |
> (1 row)
>
> test=> select * from test where network = '155.198/16';
>  network | netcol
> ---------+--------
> (0 rows)


pgsql-general by date:

Previous
From: Martin Neimeier
Date:
Subject: Jobs with PostgreSQL
Next
From: Jules Bean
Date:
Subject: Re: Large selects handled inefficiently?