postgres.git / summary / log / commit / refs

commit    078d471a909a07bc7dc93def37b6811e236f8a84
Author:   Andres Freund <andres@anarazel.de>
Date:     Thu Sep 24 12:53:33 2015 +0000
First released in: 9.6.0, 9.0.23, 9.1.19, 9.2.14, 9.3.10, 9.4.5, 9.5.0

    Lower *_freeze_max_age minimum values.
    
    The old minimum values are rather large, making it time consuming to
    test related behaviour. Additionally the current limits, especially for
    multixacts, can be problematic in space-constrained systems. 10000000
    multixacts can contain a lot of members.
    
    Since there's no good reason for the current limits, lower them a good
    bit. Setting them to 0 would be a bad idea, triggering endless vacuums,
    so still retain a limit.
    
    While at it fix autovacuum_multixact_freeze_max_age to refer to
    multixact.c instead of varsup.c.
    
    Reviewed-By: Robert Haas
    Discussion: CA+TgmoYmQPHcrc3GSs7vwvrbTkbcGD9Gik=OztbDGGrovkkEzQ@mail.gmail.com
    Backpatch: 9.0 (in parts)


 src/backend/utils/misc/guc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c
index 597ac8885e0..b03735083ec 100644
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -1973,7 +1973,7 @@ static struct config_int ConfigureNamesInt[] =
 		},
 		&autovacuum_freeze_max_age,
 		/* see pg_resetxlog if you change the upper-limit value */
-		200000000, 100000000, 2000000000, NULL, NULL
+		200000000, 100000, 2000000000, NULL, NULL
 	},
 	{
 		/* see max_connections */


[parent: c69e7d5c78af]