| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> | 
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Incrementing INET fields | 
| Date: | 2006-11-27 14:42:01 | 
| Message-ID: | 20061127144201.GD20371@phlogiston.dyndns.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Mon, Nov 27, 2006 at 03:04:01PM +0200, Peter Nixonn wrote:
> Is there some technical reason (other than finite developer time) that this
> isn't possible at present?
I don't think it makes much sense, without a fair amount of policy
around it.  For instance, you'd need to know what to increment to
when you get to 10.1.1.254/32.  Moreover, the mask range work you
mentioned as "icing on the cake" is not icing at all: it's part of
the cake, becase CIDR has been here for a long time.  So you _have_
to be able to know what range you're in in order to do autoincrement.
You could write a function that would do all this for you, though.
A
-- 
Andrew Sullivan  | ajs(at)crankycanuck(dot)ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well. 
		--Dennis Ritchie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-11-27 14:45:59 | Re: Potential to_char localization bug | 
| Previous Message | Andrew Sullivan | 2006-11-27 14:35:32 | Re: [CORE] RC1 blocker issues |