From 13fe298ca06f5390df5edf073cf401f9f0b67458 Mon Sep 17 00:00:00 2001
From: Simon Riggs <simon@2ndQuadrant.com>
Date: Fri, 22 Mar 2013 12:01:16 +0000
Subject: [PATCH] Change commit_delay to be SUSET for 9.3+ Prior to 9.3 the
commit_delay affected only the current user, whereas now only the group
leader waits while holding the WALWriteLock. Deliberate or accidental
settings to a poor value could seriously degrade performance for all users.
Privileges may be delegated by SECURITY DEFINER functions for anyone that
needs per-user settings in real situations. Request for change from Peter
Geoghegan
---
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 5246fc5b201..e1b65256a4f 100644
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -2042,7 +2042,7 @@ static struct config_int ConfigureNamesInt[] =
},
{
- {"commit_delay", PGC_USERSET, WAL_SETTINGS,
+ {"commit_delay", PGC_SUSET, WAL_SETTINGS,
gettext_noop("Sets the delay in microseconds between transaction commit and "
"flushing WAL to disk."),
NULL
--
GitLab