public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: jian he <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS
Date: Sat, 6 Sep 2025 22:03:05 -0700
Message-ID: <CAKFQuwbzmyEfdJ=LHeBEy0H1A2OYvWu-sOxsG+_qQc+ZZiOJog@mail.gmail.com> (raw)
In-Reply-To: <CACJufxG3M3W0Da+yRmu0Wj8mTUDTiEhtScsDFHb5xKfcDXWSZg@mail.gmail.com>
References: <CACJufxG3M3W0Da+yRmu0Wj8mTUDTiEhtScsDFHb5xKfcDXWSZg@mail.gmail.com>
On Saturday, September 6, 2025, jian he <[email protected]> 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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS
In-Reply-To: <CAKFQuwbzmyEfdJ=LHeBEy0H1A2OYvWu-sOxsG+_qQc+ZZiOJog@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox