The default is the setting of locale if specified otherwise the same setting as the template database. Specifies the ICU locale (see Section 24.2.2.3.2) for the database default collation order and character classification, overriding the setting locale. If locale_provider is libc, also sets the default character classification to use in the new database, overriding the setting locale. The default is the setting of locale if specified, otherwise the same setting as the template database. Sets LC_CTYPE in the database server's operating system environment. If locale_provider is libc, also sets the default collation order to use in the new database, overriding the setting locale. Sets LC_COLLATE in the database server's operating system environment. If you want to make them the default for a specific database, you can use ALTER DATABASE. 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. See Section 24.2.2.3.1 and Section 24.2.2.3.2 for details.Ĭan be overridden by setting lc_collate, lc_ctype, or icu_locale individually. The default is the same setting as the template database. Also sets the associated aspects of the operating system environment, LC_COLLATE and LC_CTYPE. Character classification affects the categorization of characters, e.g., lower, upper, and digit. Collation 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. Sets the default collation order and character classification in the new database. In some situations, this may have a noticeable negative impact on overall system performance. While this does reduce the write-ahead log volume substantially, especially if the template database is large, it also forces the system to perform a checkpoint both before and after the creation of the new database. Each such record represents copying an entire directory to a new location at the filesystem level. This strategy writes a small record to the write-ahead log for each tablespace used by the target database. The older FILE_COPY strategy is also available. ![]() This is the most efficient strategy in cases where the template database is small, and therefore it is the default. If the WAL_LOG strategy is used, the database will be copied block by block and each block will be separately written to the write-ahead log. ![]() Strategy to be used in creating the new database. The character sets supported by the PostgreSQL server are described in Section 24.3.1. Specify a string constant (e.g., 'SQL_ASCII'), or an integer encoding number, or DEFAULT to use the default encoding (namely, the encoding of the template database). encoding #Ĭharacter set encoding to use in the new database. ![]() The name of the template from which to create the new database, or DEFAULT to use the default template ( template1). To create a database owned by another role, you must be able to SET ROLE to that role. The role name of the user who will own the new database, or DEFAULT to use the default (namely, the user executing the command).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |