Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: <50f693ad-faec-4b1b-8de5-88dc90b236b4@uni-muenster.de>
Date: Fri, 13 Feb 2026 09:29:08 +0800
Cc: Fujii Masao <masao.fujii@gmail.com>,
 Matheus Alcantara <matheusssilv97@gmail.com>,
 "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5D95968-7484-461B-AA32-273C9161E9B2@gmail.com>
References: <e08cb97f-0364-4002-9cda-3c16b42e4136@uni-muenster.de>
 <DGD24UA7LASG.11H30IV2AFVA2@gmail.com>
 <CAHGQGwF-uuKkon8Ah9dbMiGKoYmFJyHZnDa_HcWWCXKnh7LJ2Q@mail.gmail.com>
 <50f693ad-faec-4b1b-8de5-88dc90b236b4@uni-muenster.de>
To: Jim Jones <jim.jones@uni-muenster.de>
Archived-At: <https://www.postgresql.org/message-id/A5D95968-7484-461B-AA32-273C9161E9B2%40gmail.com>
Precedence: bulk


> On Feb 12, 2026, at 23:33, Jim Jones <jim.jones@uni-muenster.de> =
wrote:
>=20
>=20
>=20
> On 12/02/2026 16:08, Fujii Masao wrote:
>> On Thu, Feb 12, 2026 at 11:36=E2=80=AFPM Matheus Alcantara
>> <matheusssilv97@gmail.com> wrote:
>>> The patch fix the issue and it seems correct to me.
>=20
> Thanks for the review!
>=20
>> The documentation [1] states that INCLUDING COMMENTS copies comments =
for
>> the copied columns, constraints, and indexes. It does not mention =
copying
>> comments on the table itself. Therefore, not copying table comments =
with
>> INCLUDING COMMENTS does not appear to be a bug. That is, the proposed =
patch
>> seems more like an improvement than a bug fix.
>=20
> Hmm, it seemed so obvious to me that I didn=E2=80=99t look more =
closely at the
> documentation :) Although I struggle to see the rationale for not
> copying a table=E2=80=99s comment in a CREATE TABLE LIKE ... INCLUDING =
COMMENTS
> statement, I have to agree that the documentation is quite clear about
> this limitation, and therefore it cannot really be considered a bug.
> That said, it may well be worth considering for a future release.
>=20
> What are your thoughts?
>=20
> Thanks!
>=20
> Best, Jim
>=20
>=20

I feel the current behavior is proper. When you create a table using =
LIKE, you are cloning the structure, not the identity. Just as you have =
to pick a new name for the table, you should provide a new comment that =
fits its specific purpose. If a comment is needed, the COMMENT ON =
command is already the straightforward way to handle that.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/