On Mon, 2006-12-11 at 09:18 -0700, Jonathan Ellis wrote:
> I have a table of log messages. They are mostly in the 100-200
> character length, which apparently isn't large enough for PG to want
> to compress it (length == octet_length). I really need to save disk
> space. I can store it as a bytea and compress it manually (zlib level
> 1 compression gives about 50% savings), but is there a way to force
> pg's own compression before I resort to this?
>
Are you sure PostgreSQL isn't compressing it? I didn't think there was a
minimum threshold for compression.
Regards,
Jeff Davis
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
