![]() If true, then this database can be cloned by any user with CREATEDB privileges if false (the default), then only superusers or the owner of the database can clone it. How many concurrent connections can be made to this database. The default is true, allowing connections (except as restricted by other mechanisms, such as GRANT/ REVOKE CONNECT). If false then no one can connect to this database. See CREATE TABLESPACE for more information. This tablespace will be the default tablespace used for objects created in this database. The name of the tablespace that will be associated with the new database, or DEFAULT to use the template database's tablespace. The default is to use the character classification of the template database. This affects the categorization of characters, e.g., lower, upper and digit. lc_ctypeĬharacter classification ( LC_CTYPE) to use in the new database. The default is to use the collation order of the template database. This affects the sort order applied to strings, e.g., in queries with ORDER BY, as well as the order used in indexes on text columns. lc_collateĬollation order ( LC_COLLATE) to use in the new database. If you want to make them the default for a specific database, you can use ALTER DATABASE. The character set for each database is stored in the pg_database system catalog therefore, to find out what character encoding a database is using, you can query this catalog.The other locale settings lc_messages, lc_monetary, lc_numeric, and lc_time are not fixed per database and are not set by this command. If you plan to create databases with different character encodings than the locale set for the database cluster, you should use C for the database cluster locale. For example, if your database cluster is set to the Spanish (Spain) locale, it is expected the encoding for your databases is LATIN1 (Western European languages), LATIN9 (LATIN1 plus Euro and accents), WIN1252 (Western European languages, Windows only), or UTF-8 (all languages). The locale you set implies that a corresponding character set is used for your databases. It is not recommended to designate a database character encoding that contradicts the locale set for the database cluster. However, be aware that UTF-8 character encoding requires more storage space than most other character sets. ESRI recommends you use the UTF-8 character set because it allows you to store all supported encodings. If you do not specify a different character set when you create the database, the character set of the PostgreSQL template database is used. To do this, specify the encoding option (-E) when issuing the createdb command. You specify a character set for the PostgreSQL database cluster, but you can also specify different character sets for each database. In addition to the locale, designate a character set for your databases. To learn how to alter the other locale settings, consult the PostgreSQL documentation. The first two subcategories, LC_COLLATE and LC_CTYPE, cannot be changed after the PostgreSQL instance is created. LC_TIME-Determines date and time formatting. ![]() ![]() LC_NUMERIC-Determines number formatting.LC_MONETARY-Determines the formatting of currency. ![]() The locale is composed of the following six subcategories: A C locale is the most flexible when an international environment is needed. PostgreSQL database clusters (the PostgreSQL instance) are created by default to use the standard C locale functionality of the operating system on which PostgreSQL is installed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |