Search Postgresql Archives

Re: inet/cidr ipv6 operations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 29, 2013 at 9:34 PM, George Shuklin
<george.shuklin@xxxxxxxxx> wrote:
> But IPv6 is differ. Let's assume we wants to get 'next' /64 range. Current
> range is inet'2a00:ab00:0:1/64'. We want next.
>
> Postgres do not allow adding inet + inet, so we need to add natural number.
> But 'next' /64 is 'just' 2^64. And postgres rejecting that operations
> because N is too large. ... And under some conditions we can use even /56 or
> /48 - which is really large numbers.
>
> If postgres allows to do something like that: inet'2a00:ab00:0:1/64' +
> inet'0:0:0:1/64' it should make life much easy.

Or alternatively, does PostgreSQL have any integer type larger than
64-bit bigint? I've become accustomed to using bignums in most of my
programming; arbitrary-precision integers allow all sorts of handy
flexibilities. Are there any plans to add bignums (something like
GMP's mpz) to the engine?

ChrisA


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux