On 3 November 2015 at 23:04, Bill Moran <wmo...@potentialtech.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

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to