| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS |
| Date: | 2025-09-07 05:03:05 |
| Message-ID: | CAKFQuwbzmyEfdJ=LHeBEy0H1A2OYvWu-sOxsG+_qQc+ZZiOJog@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Saturday, September 6, 2025, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> hi.
>
> https://www.postgresql.org/docs/devel/sql-createtable.
> html#SQL-CREATETABLE-PARMS-LIKE-OPT-COMMENTS
> """
> INCLUDING COMMENTS
> Comments for the copied columns, constraints, and indexes will be copied.
> The
> default behavior is to exclude comments, resulting in the copied columns
> and
> constraints in the new table having no comments.
> """
>
> The above description should mention that comments on extended
> statistics will be
> copied as well?
>
>
How about “If specified, existing comments on any copied elements are
copied as well.” ? Let’s fix this by removing the duplication of the list
of things allowed to be copied, not by fixing the oversight the duplication
permitted.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2025-09-08 07:30:37 | Re: SELECT List with/without parentheses |
| Previous Message | jian he | 2025-09-07 03:02:10 | CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS |