From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/infoschema-character-sets.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/src/sgml/html/infoschema-character-sets.html') diff --git a/doc/src/sgml/html/infoschema-character-sets.html b/doc/src/sgml/html/infoschema-character-sets.html index ea75a22..ef3ad3c 100644 --- a/doc/src/sgml/html/infoschema-character-sets.html +++ b/doc/src/sgml/html/infoschema-character-sets.html @@ -1,5 +1,5 @@ -37.7. character_sets
37.7. character_sets
Prev UpChapter 37. The Information SchemaHome Next

37.7. character_sets

+37.7. character_sets

37.7. character_sets
Prev UpChapter 37. The Information SchemaHome Next

37.7. character_sets

The view character_sets identifies the character sets available in the current database. Since PostgreSQL does not support multiple character sets within one database, this view only @@ -14,8 +14,8 @@

character encoding form

An encoding of some character repertoire. Most older character repertoires only use one encoding form, and so there are no - separate names for them (e.g., LATIN1 is an - encoding form applicable to the LATIN1 + separate names for them (e.g., LATIN2 is an + encoding form applicable to the LATIN2 repertoire). But for example Unicode has the encoding forms UTF8, UTF16, etc. (not all supported by PostgreSQL). Encoding forms are not exposed @@ -83,4 +83,4 @@ settings of the current database. If there is no such collation, then this column and the associated schema and catalog columns are null. -


Prev Up Next
37.6. attributes Home 37.8. check_constraint_routine_usage
\ No newline at end of file +


Prev Up Next
37.6. attributes Home 37.8. check_constraint_routine_usage
\ No newline at end of file -- cgit v1.2.3