| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pluggable compression support |
| Date: | 2013-06-16 12:17:51 |
| Message-ID: | CA+U5nMKVhd6+6d8ajiZTSbjUbmhfUioNjFu+K0mDrJ9W8pv9tQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15 June 2013 12:25, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
> additionally it *could* have the property Simon proposed earlier
> of *uncompressed* pages having some predetermined size, so we
> could retain optimisations of substring() even on compressed TOAST
> values.
That wasn't about having fixed size pages, it was about having a
function to determine the split points. Reason being we want to use
some intelligence to split up JSON and XML documents.
I would also like to be able to do other types of processing on fields
before they are stored.
That is probably best done as a sequence of processing transforms,
rather than a single compression module.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-06-16 12:21:06 | Re: dynamic background workers |
| Previous Message | Simon Riggs | 2013-06-16 11:49:26 | Re: pluggable compression support |