File: control

package info (click to toggle)
ip4r 1.03-2
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 140 kB
  • ctags: 232
  • sloc: ansic: 1,411; makefile: 51
file content (38 lines) | stat: -rw-r--r-- 1,623 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Source: ip4r
Section: misc
Priority: extra
Maintainer: Robert S. Edmonds <edmonds@debian.org>
Build-Depends: debhelper (>= 5.0.0), postgresql-server-dev-8.3
Standards-Version: 3.7.3

Package: postgresql-8.3-ip4r
Architecture: any
Depends: ${shlibs:Depends}
Recommends: postgresql-8.3
Description: IPv4 and IPv4 range index types for PostgreSQL 8.3
 This PostgreSQL module provides two data types, ip4 and ip4r, which can
 contain a single IPv4 address or a range of IPv4 addresses,
 respectively.
 .
 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