2020년 6월 5일 (금) 오후 9:45, 이동욱 <sh95...@gmail.com>님이 작성:
> I've modified my previous patch because it linked the wrong document so I
> fixed it. and I add a highlight to the encoding list for readability.
>
> What do you think about this change?
>
> Thanks,
> Dong Wook
>
> 2020년 6월 4일 (목) 오후 10:20, 이동욱 <sh95...@gmail.com>님이 작성:
>
>> To let users know what kind of character set
>> can be used add examples and a link to --encoding option.
>>
>> Thanks,
>> Dong wook
>>
>
From 890ab97aa211dc6fe99ce54bc5522afd5d614081 Mon Sep 17 00:00:00 2001
From: Lee Dong Wook <sh95119@gmail.com>
Date: Thu, 4 Jun 2020 21:54:33 +0900
Subject: [PATCH] pg_dump: Add example and link for --encoding option
To let users know what kind of character set
can be used add examples and a link to --encoding option.
---
doc/src/sgml/ref/pg_dump.sgml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 197b5c0d70..9915f35f14 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -226,6 +226,8 @@ PostgreSQL documentation
the dump is created in the database encoding. (Another way to get the
same result is to set the <envar>PGCLIENTENCODING</envar> environment
variable to the desired dump encoding.)
+ You can also use variable character set (<envar>i.e. UTF8, EUC_KR, EUC_JP, EUC_CN ... etc</envar>)
+ and you can see the all supported character set in PostgreSQL (see <xref linkend="multibyte-charset-supported"/>)
</para>
</listitem>
</varlistentry>
--
2.23.0
