From: Heikki Linnakangas <heikki@enterprisedb.com>
Date: Wed, 1 Apr 2009 09:17:32 +0000 (+0000)
Subject: Update comment to reflect that LC_COLLATE and LC_CTYPE are now
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=d63cd7695900e7176bba696f177483561c1dca0e;p=users%2Fsimon%2Fpostgres.git

Update comment to reflect that LC_COLLATE and LC_CTYPE are now
per-database settings.
---

diff --git a/src/backend/utils/adt/pg_locale.c b/src/backend/utils/adt/pg_locale.c
index 7ee280834d..118a6fea52 100644
--- a/src/backend/utils/adt/pg_locale.c
+++ b/src/backend/utils/adt/pg_locale.c
@@ -11,9 +11,9 @@
 
 /*----------
  * Here is how the locale stuff is handled: LC_COLLATE and LC_CTYPE
- * are fixed by initdb, stored in pg_control, and cannot be changed.
- * Thus, the effects of strcoll(), strxfrm(), isupper(), toupper(),
- * etc. are always in the same fixed locale.
+ * are fixed at CREATE DATABASE time, stored in pg_database, and cannot 
+ * be changed. Thus, the effects of strcoll(), strxfrm(), isupper(),
+ * toupper(), etc. are always in the same fixed locale.
  *
  * LC_MESSAGES is settable at run time and will take effect
  * immediately.