Re: COMMENTS are not being copied in CREATE TABLE LIKE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Alex Liapychev <coder(dot)sam(at)gmail(dot)com>, matheusssilv97 <matheusssilv97(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, "masao(dot)fujii" <masao(dot)fujii(at)gmail(dot)com>, "david(dot)g(dot)johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "huseyin(dot)d3r" <huseyin(dot)d3r(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, chochoforwork(at)gmail(dot)com, 44973863(at)qq(dot)com
Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE
Date: 2026-10-01 17:45:38
Message-ID: 1113328.1790876738@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(at)vondra(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-10-01 18:00:00 Re: Stabilize recovery conflict stats checks in 031_recovery_conflict.pl
Previous Message Etsuro Fujita 2026-10-01 17:37:29 Re: postgres_fdw: transaction mode inheritance corner cases