Doc: fix oversights in "Client/Server Character Set Conversions" table.
authorTom Lane
Sat, 1 Sep 2018 20:02:47 +0000 (16:02 -0400)
committerTom Lane
Sat, 1 Sep 2018 20:02:47 +0000 (16:02 -0400)
This table claimed that JOHAB could be used as a server encoding, which
was true originally but hasn't been true since 8.3.  It also lacked
entries for EUC_JIS_2004 and SHIFT_JIS_2004.

JOHAB problem noted by Lars Kanis, the others by me.

Discussion: https://postgr.es/m/c0f514a1-b7a9-b9ea-1c02-c34aead56c06@greiz-reinsdorf.de

doc/src/sgml/charset.sgml

index dc3fd34a62414d1a0b12a62a86d198d383c7c296..a6143ef8a744e8db8c9024e07902a14a47a3da59 100644 (file)
@@ -1483,6 +1483,13 @@ $ psql -l
          UTF8
          
         
+        
+         EUC_JIS_2004
+         EUC_JIS_2004,
+         SHIFT_JIS_2004,
+         UTF8
+         
+        
         
          EUC_KR
          EUC_KR,
@@ -1538,8 +1545,7 @@ $ psql -l
         
         
          JOHAB
-         JOHAB,
-         UTF8
+         not supported as a server encoding
          
         
         
@@ -1645,6 +1651,11 @@ $ psql -l
          not supported as a server encoding
          
         
+        
+         SHIFT_JIS_2004
+         not supported as a server encoding
+         
+        
         
          SQL_ASCII
          any (no conversion will be performed)