From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: forcing compression of text field |
Date: | 2006-12-12 15:25:35 |
Message-ID: | 457EC9EF.8090507@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/11/06 10:18, 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?
What can be compressed? Trailing whitespace or repeating substrings?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFfsnvS9HxQb37XmcRAuaeAKDRv9IUDH4zenHoVQPST0vFbpHLkwCdED9k
rvvOkNCRx/J8EkGtBF2Bs9Y=
=XANI
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2006-12-12 15:28:48 | Re: Why DISTINCT ... DESC is slow? |
Previous Message | Brad Nicholson | 2006-12-12 15:25:17 | Unrecognized time zone name error. |