Commit d7ee3355 authored by Tom Lane's avatar Tom Lane

Tweak a comment to agree a bit better with the new dispensation that

locales are database-wide, not server-wide.
parent 2fe0f296
...@@ -13,7 +13,7 @@ ...@@ -13,7 +13,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.222 2009/04/23 17:39:21 tgl Exp $ * $PostgreSQL: pgsql/src/backend/commands/dbcommands.c,v 1.223 2009/05/05 23:39:55 tgl Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
...@@ -332,10 +332,12 @@ createdb(const CreatedbStmt *stmt) ...@@ -332,10 +332,12 @@ createdb(const CreatedbStmt *stmt)
errmsg("invalid locale name %s", dbctype))); errmsg("invalid locale name %s", dbctype)));
/* /*
* Check whether encoding matches server locale settings. We allow * Check whether chosen encoding matches chosen locale settings. This
* mismatch in three cases: * restriction is necessary because libc's locale-specific code usually
* fails when presented with data in an encoding it's not expecting.
* We allow mismatch in three cases:
* *
* 1. ctype_encoding = SQL_ASCII, which means either that the locale is * 1. locale encoding = SQL_ASCII, which means either that the locale is
* C/POSIX which works with any encoding, or that we couldn't determine * C/POSIX which works with any encoding, or that we couldn't determine
* the locale's encoding and have to trust the user to get it right. * the locale's encoding and have to trust the user to get it right.
* *
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment