From: | 이동욱 <sh95119(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: [PATCH] pg_dump: Add example and link for --encoding option |
Date: | 2020-06-05 12:45:52 |
Message-ID: | CAAcBya+GRbHTybkMkH88ZCg-=y8tij8N+2CoPF1Kneb024s84Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
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, 이동욱 <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.
>
> Thanks,
> Dong wook
>
Attachment | Content-Type | Size |
---|---|---|
v2-0001-pg_dump-Add-example-and-link-for-encoding-option.patch | application/octet-stream | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2020-06-05 14:31:34 | create database with template doesn't copy ACL |
Previous Message | PG Doc comments form | 2020-06-05 11:16:59 | Documentation 9.8. Data Type Formatting Functions: missing behaviour on invalid input at to_date() |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2020-06-05 13:04:31 | Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 |
Previous Message | chenhj | 2020-06-05 12:39:46 | Re: [Proposal] Page Compression for OLTP |