From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values. |
Date: | 2015-10-05 13:39:58 |
Message-ID: | 15337.1444052398@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-09-24 12:39:54 -0300, Alvaro Herrera wrote:
>> I'm surprised the error has survived this long. Without checking I
>> can't say what's the best solution either, but I would opt for
>> documenting the limits we have -- if we want to change them back to 0 I
>> say that merits its own discussion.
> How about simply removing that sentence? I.e. something like
> <literal>autovacuum_freeze_max_age</> larger than the system-wide setting
> - (it can only be set smaller). Note that while you can set
> - <literal>autovacuum_freeze_max_age</> very small, or even zero, this is
> - usually unwise since it will force frequent vacuuming.
> + (it can only be set smaller).
> </para>
How about "Setting autovacuum_freeze_max_age to very small values
is unwise since it will force frequent vacuuming."
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-10-05 13:45:39 | Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values. |
Previous Message | Stephen Frost | 2015-10-05 11:55:28 | pgsql: Apply SELECT policies in INSERT/UPDATE+RETURNING |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-10-05 13:45:39 | Re: [COMMITTERS] pgsql: Lower *_freeze_max_age minimum values. |
Previous Message | Heikki Linnakangas | 2015-10-05 13:02:41 | Use EVP API pgcrypto encryption, dropping support for OpenSSL 0.9.6 and older |