From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chris Angelico <rosuav(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: inet/cidr ipv6 operations |
Date: | 2013-01-29 15:16:20 |
Message-ID: | 28803.1359472580@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Chris Angelico <rosuav(at)gmail(dot)com> writes:
> 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?
It's hard to muster much excitement about that when we've already
got "numeric".
As far as the OP's problem goes, I wonder if there wouldn't be some use
in an inet+(big)int function that does shift-and-add, ie move the
integer over by the number of bits that have to remain zero according to
the netmask. I'm not seeing the use for adding enormous random integers
to IP addresses --- but "three over from this /64 block" doesn't seem so
improbable.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-01-29 15:22:29 | Re: JDBC connection test with SSL on PG 9.2.1 server |
Previous Message | Chris Angelico | 2013-01-29 15:05:38 | Re: inet/cidr ipv6 operations |