aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/variable.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-10-07 12:36:00 +0900
committerMichael Paquier <michael@paquier.xyz>2024-10-07 12:36:00 +0900
commit2e7c4abe5a88a1528236a13c9ef2e351a97fa022 (patch)
treeaf4ac29071ff067a497da6a1a7c4b4951c7951b6 /src/backend/commands/variable.c
parentf8d9a9f21e2fec4f67af7b430b981b6e6e7a0906 (diff)
downloadpostgresql-2e7c4abe5a88a1528236a13c9ef2e351a97fa022.tar.gz
postgresql-2e7c4abe5a88a1528236a13c9ef2e351a97fa022.zip
Use camel case for "DateStyle" in some error messages
This GUC is written as camel-case in most of the documentation and the GUC table (but not postgresql.conf.sample), and two error messages hardcoded it with lower case characters. Let's use a style more consistent. Most of the noise comes from the regression tests, updated to reflect the GUC name in these error messages. Author: Peter Smith Reviewed-by: Peter Eisentraut, Álvaro Herrera Discussion: https://postgr.es/m/CAHut+Pv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w@mail.gmail.com
Diffstat (limited to 'src/backend/commands/variable.c')
-rw-r--r--src/backend/commands/variable.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/variable.c b/src/backend/commands/variable.c
index 27ce7d3f8fc..7df26942aff 100644
--- a/src/backend/commands/variable.c
+++ b/src/backend/commands/variable.c
@@ -182,7 +182,7 @@ check_datestyle(char **newval, void **extra, GucSource source)
if (!ok)
{
- GUC_check_errdetail("Conflicting \"datestyle\" specifications.");
+ GUC_check_errdetail("Conflicting \"DateStyle\" specifications.");
return false;
}