| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC/WIP: adding new configuration options to TOAST |
| Date: | 2015-11-04 01:21:58 |
| Message-ID: | CAMsr+YHQj9S0c=____Sc43iThEaSkPXpWADbq4pDt44VfFYGjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 November 2015 at 23:04, Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
>
> Looking for feedback to see if anyone sees any issues or has any
> suggestions on what I'm doing. The attached patch alters 3 things
> with regard to TOAST behavior:
COMPRESSION_TEST_SIZE (2) seems useful.
The other two mostly seem like options nobody's going to know are
there, or know how to sensibly set if they do notice them. What's the
driving reason behind those, the problem you're trying to solve? Why
make them configurable per-table (or at all)?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-11-04 01:44:14 | Re: PoC: Partial sort |
| Previous Message | Haribabu Kommi | 2015-11-04 00:36:42 | Re: BUG #13741: vacuumdb does not accept valid password |