Attached. Per discussion on the thread "Redesigning checkpoint_segments" this raises the default for the new parameter "max_wal_size" to 1GB.
Seems too small to add it to the CF, but if you want me to, I will. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c new file mode 100644 index d84dba7..cc4654a *** a/src/backend/utils/misc/guc.c --- b/src/backend/utils/misc/guc.c *************** static struct config_int ConfigureNamesI *** 2171,2177 **** GUC_UNIT_XSEGS }, &max_wal_size, ! 8, 2, INT_MAX, NULL, assign_max_wal_size, NULL }, --- 2171,2177 ---- GUC_UNIT_XSEGS }, &max_wal_size, ! 64, 2, INT_MAX, NULL, assign_max_wal_size, NULL }, diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample new file mode 100644 index f8f9ce1..b4bc29a *** a/src/backend/utils/misc/postgresql.conf.sample --- b/src/backend/utils/misc/postgresql.conf.sample *************** *** 198,204 **** # - Checkpoints - #checkpoint_timeout = 5min # range 30s-1h ! #max_wal_size = 128MB # in logfile segments #min_wal_size = 80MB #checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0 #checkpoint_warning = 30s # 0 disables --- 198,204 ---- # - Checkpoints - #checkpoint_timeout = 5min # range 30s-1h ! #max_wal_size = 1GB # in logfile segments #min_wal_size = 80MB #checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0 #checkpoint_warning = 30s # 0 disables
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
