From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: extensible external toast tuple support & snappy prototype |
Date: | 2013-06-07 16:07:23 |
Message-ID: | 24229.1370621243@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-06-07 11:46:45 -0400, Tom Lane wrote:
>> IME, once we've changed it once, the odds that we'll want to change it
>> again go up drastically. I think if we're going to make a change here
>> we should leave room for future revisions.
> The above bit was just about how much control we give the user over the
> compression algorithm used for compressing new data. If we just add one
> method atm which we think is just about always better than pglz there's
> not much need to provide the tunables already.
Ah, ok, I thought you were talking about storage-format decisions not
about whether to expose a tunable setting.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2013-06-07 16:12:56 | Re: extensible external toast tuple support & snappy prototype |
Previous Message | Alvaro Herrera | 2013-06-07 16:02:28 | Re: extensible external toast tuple support & snappy prototype |