From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "tschak" <jochen(dot)schlosser(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: this is what i meant |
Date: | 2006-01-17 05:05:34 |
Message-ID: | 24433.1137474334@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"tschak" <jochen(dot)schlosser(at)gmail(dot)com> writes:
> Can I explicitly store 4 Bit (FIXED lenght) in a column without
> "wasting" space?
No. There is no provision in Postgres for data types occupying less
than a byte. You'll need to think about merging those columns together.
> Alright... so I do not need the OIDs! But as for as I know I need OIDs
> if I want to use a BLOB for the complete information, which I would
> like to do once again to reduce the size of each row in the table (from
> 80 *4 Bits down to just 1 Pointer to the BLOB).
You are confusing OIDs with BLOBs ... they are not the same thing.
There are a couple different ways of handling BLOBs in Postgres: bytea
values and "large objects". For the most part I'd suggest bytea, though
if you need cheap access to sub-sections of a BLOB, large objects would
be the way to go.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | R, Rajesh (STSD) | 2006-01-17 07:07:17 | Re: [PATCH] Better way to check for getaddrinfo function. |
Previous Message | Christopher Browne | 2006-01-17 03:35:24 | Re: Create/Erase 5000 Tables in PostGRE SQL in execution |