Tom Lane wrote: > It would be fairly easy, I think, to add some reloption fields that > would let these parameters be controlled on a per-table level. > Per-column would be much more painful; do we really need that? >
Another +1 on the per-table setting. Or a config file setting to disable this for the instance. We have a 200GB DB that is mostly large text (>1MB) that is not searched with substr. If we see a blowout in size of even 3x, we will not be able to upgrade due to disk space limitations (at least without paying for a lot of disks on mirror servers and hot-standy servers). -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
