stig erikson wrote:
> by the way, can i enable table compression in some way?
> i could not find it in the manual, found only compression for backups
> and EXTENDED column storage, but nothing for integers.
No, you can't compress fixed-length data types using the TOAST
mechanism.
--
Peter Eisen
Peter Eisentraut wrote:
PostgreSQL Bugs List wrote:
why is this feature important?
having in mind the development of datawarehouses with huge amount of
data (hundreds of millions, or billions of rows in fact tables) every
byte is of importance.
Yet how many applications could make use of the limit
PostgreSQL Bugs List wrote:
> why is this feature important?
> having in mind the development of datawarehouses with huge amount of
> data (hundreds of millions, or billions of rows in fact tables) every
> byte is of importance.
Yet how many applications could make use of the limited range that a
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> for the next version of postgresql i would like to see support for 1-byte
> integers (signed and unsigned) and also for 4-bit (1/2-byte) integers
> (signed and unsigned).
See the "char" type (not to be confused with char(n)) and the bitstring
The following bug has been logged online:
Bug reference: 1257
Logged by: stig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: all
Description:add support for 1-byte integer and 4-bit integer
Details:
hello, i could not find this
