From 77f7763b55a89254f3b4be1f92402188bf2575b8 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut
Date: Tue, 3 Sep 2002 21:45:44 +0000
Subject: Remove all traces of multibyte and locale options.  Clean up comments
 referring to "multibyte" where it really means character encoding.

---
 src/backend/utils/init/postinit.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

(limited to 'src/backend/utils/init')

diff --git a/src/backend/utils/init/postinit.c b/src/backend/utils/init/postinit.c
index 8be88ac259f..7de6eb2595d 100644
--- a/src/backend/utils/init/postinit.c
+++ b/src/backend/utils/init/postinit.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/init/postinit.c,v 1.114 2002/09/02 02:47:05 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/init/postinit.c,v 1.115 2002/09/03 21:45:42 petere Exp $
  *
  *
  *-------------------------------------------------------------------------
@@ -69,7 +69,7 @@ static bool ThereIsAtLeastOneUser(void);
  * creating any serious problems.
  *
  * This is also a handy place to fetch the database encoding info out
- * of pg_database, if we are in MULTIBYTE mode.
+ * of pg_database.
  *
  * To avoid having to read pg_database more times than necessary
  * during session startup, this place is also fitting to set up any
@@ -124,9 +124,8 @@ ReverifyMyDatabase(const char *name)
 			 name);
 
 	/*
-	 * OK, we're golden.  Only other to-do item is to save the MULTIBYTE
-	 * encoding info out of the pg_database tuple --- or complain, if we
-	 * can't support it.
+	 * OK, we're golden.  Only other to-do item is to save the
+	 * encoding info out of the pg_database tuple.
 	 */
 	SetDatabaseEncoding(dbform->encoding);
 	/* If we have no other source of client_encoding, use server encoding */
-- 
cgit v1.2.3