| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Shaun Thomas <shaun(dot)thomas(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Steele <david(at)pgmasters(dot)net> |
| Subject: | Re: Re: A separate table level option to control compression |
| Date: | 2019-04-06 07:18:48 |
| Message-ID: | 20190406071848.GD2145@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 05, 2019 at 09:10:31AM -0400, Andrew Dunstan wrote:
> Well, that would be a bit sad. ISTM if we conclude that the current
> behaviour is a bug we could commit the current patch and backpatch a
> fix to honor a lower toast_tuple_threshold. But yes, time is tight.
48 hours remain, which is very tight. Let's see but the chances are
small :(
If we think that lowering toast_tuple_threshold should be supported
then the patch on the other thread should be used first, perhaps
back-patched (it lacks pieces with ALTER TABLE as pointed out as
well). If we don't use the other patch, then what's proposed on this
thread is actually wrong and should be reworked. In any case,
something is wrong.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | GUO Rui | 2019-04-06 07:26:52 | Re: Google Summer of Code: question about GiST API advancement project |
| Previous Message | Michael Paquier | 2019-04-06 07:13:53 | Re: New vacuum option to do only freezing |