Re: [PATCH] pg_dump: Add example and link for --encoding option

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: 이동욱 <sh95119(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] pg_dump: Add example and link for --encoding option
Date: 2020-07-11 11:55:19
Message-ID: 607ff92b-6aba-8835-5bbc-ead863c768c5@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On 2020-06-05 14:45, 이동욱 wrote:
> 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?

The wording in your patch needed a bit of editing but adding a link to
the supported encodings seems sensible. I have committed it with a new
wording.

>
> Thanks,
> Dong Wook
>
> 2020년 6월 4일 (목) 오후 10:20, 이동욱 <sh95119(at)gmail(dot)com
> <mailto:sh95119(at)gmail(dot)com>>님이 작성:
>
> To let users know what kind of character set
> can be used add examples and a link to --encoding option.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Stephen Frost 2020-07-11 14:22:13 Re: Default setting for enable_hashagg_disk
Previous Message David Rowley 2020-07-11 05:00:22 Re: Default setting for enable_hashagg_disk

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2020-07-11 12:14:48 Re: Binary support for pgoutput plugin
Previous Message Tomas Vondra 2020-07-11 11:24:16 Re: WIP: BRIN multi-range indexes