From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Client-side compression |
Date: | 2009-06-23 20:30:37 |
Message-ID: | 4A413B6D.5070200@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Not sure if this belongs here or on the admin or performance list.
Apologies if so. (And this may be a second posting as the first was from
an un-registered account. Further apologies)
My assumption is that any de/compression done by postgres would be
server-side.
We're considering minimizing bandwidth utilization by using client-side
compression on a column value that will typically be multi-megabyte in
size. We would use ALTER TABLE SET STORAGE EXTERNAL to prevent the
server from un-necessary compression.
Is this generally worthwhile? I haven't found any thread on the subject
of client-side compress so any pointer more than welcome.
Is there a great penalty for a query which delves into the value, given
that the server will not be aware it's compressed? I assume we're
pretty much on our own to prevent such actions (i.e. the app can never
query against this column via sql).
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Fuchs | 2009-06-24 08:37:37 | Re: Composite primary keys |
Previous Message | Tom Lane | 2009-06-23 19:15:17 | Re: Composite primary keys |