Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236]) by hub.org (8.10.1/8.10.1) with ESMTP id e5HCueM77591; Sat, 17 Jun 2000 08:56:40 -0400 (EDT) Received: from regulus.student.UU.SE ([130.238.5.2]:58071 "EHLO regulus.its.uu.se") by merganser.its.uu.se with ESMTP id ; Sat, 17 Jun 2000 14:56:03 +0200 Received: from peter (helo=localhost) by regulus.its.uu.se with local-esmtp (Exim 3.02 #2) id 133IF3-0002YH-00; Sat, 17 Jun 2000 15:02:29 +0200 Date: Sat, 17 Jun 2000 15:02:29 +0200 (CEST) From: Peter Eisentraut To: Vadim Passynkov cc: pgsql-bugs@postgresql.org, pgsql-sql@postgresql.org Subject: Re: Some problem with inet type on PostgreSQL-7.0 In-Reply-To: <39479E8E.F6F96E86@axxent.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Archive-Number: 200006/92 I can confirm your problem but there's no known fix. The truth is that the inet/cidr types have quite a number of bogosities but no one understands them well enough to undertake fixing them. Vadim Passynkov writes: > Hi All, > > I have some problem with inet type on PostgreSQL-7.0 (FreeBSD > 3.4-STABLE) > > Table "ipaddresses" > Attribute | Type | Modifier > --------------+---------+---------------------------- > sysname | text | not null > index | integer | not null > ip_addr | inet | not null > > Indices: ipaddresses_ip_addr, > ipaddresses_pkey > > (sysname, ip_addr) - PRIMARY KEY > > View "ipaddresses_view" > Attribute | Type | Modifier > --------------+---------+---------- > sysname | text | > index | integer | > ip_addr | inet | > ip_netmask | inet | > > View definition: SELECT ipaddresses.sysname, ipaddresses."index", > ipv4_host(ipaddresses.ip_addr) AS ip_addr, > ipv4_netmask(ipaddresses.ip_addr) AS ip_netmask FROM ipaddresses; > > > ipv4_host and ipv4_netmask like original host and netmask but return > inet type ( need for ORDER ) > > CREATE FUNCTION ipv4_host(inet) RETURNS inet AS ' > BEGIN > RETURN host($1); > END; > ' LANGUAGE 'plpgsql'; > > CREATE FUNCTION ipv4_netmask(inet) RETURNS inet AS ' > BEGIN > RETURN netmask($1); > END; > ' LANGUAGE 'plpgsql'; > > > **************************** Problem ************************ > > select * from ipaddresses where sysname = 'switch01.tor'; > sysname | index | ip_addr > --------------+-------+------------------ > switch01.tor | 1 | 127.0/8 > switch01.tor | 2 | 127.0/8 > switch01.tor | 3 | 209.250.155.8/27 > (2 rows) > > but (sysname, ip_addr) - PRIMARY KEY > > 127.0/8 - it's not correct output ( real 127.0.0.2/8 and 127.0.0.3/8) > > select * from ipaddresses_view where sysname = 'switch01.tor'; > sysname | index | ip_addr | ip_netmask > --------------+-------+---------------+----------------- > switch01.tor | 1 | 127.0.0.2 | 255.0.0.0 > switch01.tor | 2 | 127.0.0.3 | 255.0.0.0 > switch01.tor | 3 | 209.250.155.8 | 255.255.255.224 > (2 rows) > > > 127.0.0.2 | 255.0.0.0 and 127.0.0.3 | 255.0.0.0 - it's correct output > > And of course after pg_dump and restore correct value 127.0.0.2/8 and > 127.0.0.3/8 will lose > and will have problem with PRIMARY KEY - (sysname, ip_addr). > > -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden