ip4r 1.05-0.1 source package in Ubuntu


ip4r (1.05-0.1) unstable; urgency=low

  * Non-maintainer upload.
  * New upstream version compatible with PG 9.0.
  * Convert to use pg_buildext to build against PG 9.1;
    closes: #605711, #639470.

 -- Christoph Berg <email address hidden>  Sat, 08 Oct 2011 14:34:24 +0200

Upload details

Uploaded by:
Robert S. Edmonds on 2011-10-08
Uploaded to:
Original maintainer:
Robert S. Edmonds
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release on 2011-10-13 universe misc


File Size SHA-256 Checksum
ip4r_1.05-0.1.dsc 1.7 KiB e2716c1e3ba4b29c30e582f2b1fb0de13e9ebf42cc11265ac109271ea84de120
ip4r_1.05.orig.tar.gz 18.3 KiB 134615f2423085410b2d1a05e8e25bd46f7bf7f294470302a8d9ee2e9507b1c2
ip4r_1.05-0.1.diff.gz 2.2 KiB be555a7ca06d90c26de64c848b4e36afcf8a72715adb0a6786e6138c2c9ca9d6

No changes file available.

Binary packages built by this source

postgresql-9.1-ip4r: IPv4 and IPv4 range index types for PostgreSQL 9.1

 This PostgreSQL module provides two data types, ip4 and ip4r, which can
 contain a single IPv4 address or a range of IPv4 addresses,
 While PostgreSQL already has built-in types 'inet' and 'cidr', the
 authors of this module found that they had a number of requirements
 that were not addressed by the built-in type.
 Firstly and most importantly, the built-in types have no support for
 index lookups of the form (column >>= parameter), i.e. where you have
 a table of IP address ranges and wish to find which ones include a
 given IP address. This requires an rtree or gist index to do
 efficiently, and also requires a way to represent IP address ranges
 that do not fall precisely on CIDR boundaries.
 Secondly, the built-in inet/cidr are somewhat overloaded with
 semantics, with inet combining two distinct concepts (a netblock, and
 a specific IP within that netblock). Furthermore, they are variable
 length types (to support IPv6) with non-trivial overheads, and the
 authors (whose applications mainly deal in large volumes of single
 IPv4 addresses) wanted a more lightweight representation.
 ip4r therefore supports two distinct data types (so far):
   ip4 - a single IPv4 address
   ip4r - an arbitrary range of IPv4 addresses