pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas@vondra.me>
Cc: Jim Jones <jim.jones@uni-muenster.de>
Cc: Alex Liapychev <coder.sam@gmail.com>
Cc: matheusssilv97 <matheusssilv97@gmail.com>
Cc: Chao Li <li.evan.chao@gmail.com>
Cc: masao.fujii <masao.fujii@gmail.com>
Cc: david.g.johnston <david.g.johnston@gmail.com>
Cc: huseyin.d3r <huseyin.d3r@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Cc: chochoforwork@gmail.com
Cc: 44973863@qq.com
Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE
Date: Thu, 01 Oct 2026 13:45:38 -0400
Message-ID: <1113328.1790876738@sss.pgh.pa.us> (raw)
In-Reply-To: <6cfde153-bb97-4fa5-a7e2-6b7c2056ae5d@vondra.me>
References: <e08cb97f-0364-4002-9cda-3c16b42e4136@uni-muenster.de>
	<tencent_D0A4135EDF6E96A0D4478DABF0656D6DB408@qq.com>
	<2d41978b-3bca-4756-b0a0-b6e707ad7793@uni-muenster.de>
	<tencent_FF05EDF384FEB7852516F57BE32C7C61DB06@qq.com>
	<88b16128-d6f4-4a7b-a29a-fa0cd1c2084f@uni-muenster.de>
	<tencent_28945AA8110B3EA5AD8A366542E61BCA5205@qq.com>
	<65963A8C-C1EE-431E-9513-C4AD16AEE789@gmail.com>
	<223a6be3-3917-47a4-9b5d-51720c60ad58@vondra.me>
	<c8525e6e-5789-464e-a70d-b3916e4168eb@uni-muenster.de>
	<CAD4C109-0CAB-4D25-9C3B-FDC8CE375E4D@gmail.com>
	<36F56BBE-1499-4F82-AC03-05AAAE65D657@gmail.com>
	<6cc4ef4b-f997-4453-ab40-bc012d342fa0@uni-muenster.de>
	<6cfde153-bb97-4fa5-a7e2-6b7c2056ae5d@vondra.me>

Tomas Vondra <tomas@vondra.me> writes:
> Yes, I can construct a made-up example, but I struggle to create an
> example where copying table comments would be meaningful.

> I think this lack of use case is partially due to the origin of the
> patch. If it was written because of genuine need for the feature, we'd
> have the use case by definition. But it was written "because it's
> missing" and so no use case.

Yeah, this argument is what's bugging me.  We are struggling to figure
out what the patch should do with multiple comments because we don't
have a clear use-case in mind.  Any behavior we choose might be the
wrong one for whatever usage is out there.  So I'd just as soon pass
on implementing this functionality until we have some field requests
and we can quiz those people about their needs.

			regards, tom lane






view thread (37+ messages)  latest in thread

Message-ID: <1113328.1790876738@sss.pgh.pa.us>
Permalink:  ../1113328.1790876738@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1113328.1790876738@sss.pgh.pa.us

 · 

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: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tomas@vondra.me, jim.jones@uni-muenster.de, coder.sam@gmail.com, matheusssilv97@gmail.com, li.evan.chao@gmail.com, masao.fujii@gmail.com, david.g.johnston@gmail.com, huseyin.d3r@gmail.com, pgsql-hackers@lists.postgresql.org, chochoforwork@gmail.com, 44973863@qq.com
  Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE
  In-Reply-To: <1113328.1790876738@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox