Re: [HACKERS] compression in LO and other fields - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] compression in LO and other fields
Date
Msg-id 16202.942354490@sss.pgh.pa.us
Whole thread Raw
In response to compression in LO and other fields  (Karel Zak - Zakkr <zakkr@zf.jcu.cz>)
Responses Re: [HACKERS] compression in LO and other fields
List pgsql-hackers
Karel Zak - Zakkr <zakkr@zf.jcu.cz> writes:
>  I see the inv_api and other LO routines, and my idea is add support 
> for bzip2 stream to the inv_api and allow in current LO routines used 
> compression. It si good idea? 

LO is a dead end.  What we really want to do is eliminate tuple-size
restrictions and then have large ordinary fields (probably of type
bytea) in regular tuples.  I'd suggest working on compression in that
context, say as a new data type called "bytez" or something like that.
bytez would act just like bytea except the on-disk representation would
be compressed.  A compressed variant of type "text" would also be useful.
In the long run this will be much more useful and easier to work with
than adding another frammish to large objects.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Theo Kramer
Date:
Subject: Re: [HACKERS] Slow - grindingly slow - query
Next
From: Bryan Ingram
Date:
Subject: syncing, replicating & crash recovery Q's