Re: [GENERAL] IPv4 addresses, unsigned integers, space

2003-07-17 Thread Florian Weimer
Jim Crate <[EMAIL PROTECTED]> writes: > on 7/15/03, Florian Weimer <[EMAIL PROTECTED]> wrote: > >>If I switched from signed integers to unsigned integers (and from INET >>to "real" IPv4 addresses, consisting of the relevant 32 bits only) I >>think I could save about 25% of my table size. > > Why d

Re: [GENERAL] IPv4 addresses, unsigned integers, space

2003-07-15 Thread Florian Weimer
Bruno Wolff III <[EMAIL PROTECTED]> writes: >> Does PostgreSQL already implement these data types? I don't think so. >> If I succeed in implementing them, would you accept a patch? > > You can have unsigned integers using a domain with a check constraint. They take twice as much storage as neces

Re: [GENERAL] IPv4 addresses, unsigned integers, space

2003-07-15 Thread Bruno Wolff III
On Tue, Jul 15, 2003 at 12:59:34 +0200, Florian Weimer <[EMAIL PROTECTED]> wrote: > If I switched from signed integers to unsigned integers (and from INET > to "real" IPv4 addresses, consisting of the relevant 32 bits only) I > think I could save about 25% of my table size. > > Does PostgreSQL a

[GENERAL] IPv4 addresses, unsigned integers, space

2003-07-15 Thread Florian Weimer
If I switched from signed integers to unsigned integers (and from INET to "real" IPv4 addresses, consisting of the relevant 32 bits only) I think I could save about 25% of my table size. Does PostgreSQL already implement these data types? I don't think so. If I succeed in implementing them, would