Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqYhi-00D9Af-2S for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Feb 2026 15:34:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vqYhg-009aWC-1F for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Feb 2026 15:34:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqYhg-009aVx-0B for pgsql-hackers@lists.postgresql.org; Thu, 12 Feb 2026 15:34:04 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vqYhe-00000000KzU-3D6D for pgsql-hackers@lists.postgresql.org; Thu, 12 Feb 2026 15:34:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-muenster.de; i=@uni-muenster.de; q=dns/txt; s=uniout; t=1770910442; x=1802446442; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=9GPyowmy5/S8/CJ9KNm/CoJDouvN0xDef26cVDeHWEs=; b=GyrIQOfahqxzapepDdK5w741hd1MW4QpLvGu784WeBrqKE1uwwP5sgG7 VMF7Q3IzeC1/pdmnJZbKay3m3y8VyvtBj4ByKkY43Hl5ykNqahgT2BNeK dv4ylvEc6c6ZQGqGFPvIACptntD8YdPAWpMfAiGaNOxAAO0wGI4R5/iEY 8rjL+9klCUeIRDJTBnAaJsrLnxf+YQ1SzcZzu5mXNfESViSu7rnHAh+6P cNYFE0x9SUFRf4Xe+3eH0Y8TNNy+tp3vJVEBPBDs8WePp1Rc7ejCeaUtd FC7jtZpKorDfL0z//avEmTsrzFZDVrRosmcnDWhxa/keohnxbApeClrCX g==; X-CSE-ConnectionGUID: QYoM9vhaSnWiD5OHjzLeyQ== X-CSE-MsgGUID: wg8Nb9kNQmqhHZi3pi4qpQ== X-IronPort-AV: E=Sophos;i="6.21,286,1763420400"; d="scan'208";a="384569356" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 12 Feb 2026 16:34:01 +0100 Received: from [192.168.178.27] (dynamic-080-171-110-024.80.171.pool.telefonica.de [80.171.110.24]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id 91FCB20ADF03; Thu, 12 Feb 2026 16:34:00 +0100 (CET) Message-ID: <50f693ad-faec-4b1b-8de5-88dc90b236b4@uni-muenster.de> Date: Thu, 12 Feb 2026 16:33:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE To: Fujii Masao , Matheus Alcantara Cc: "pgsql-hackers@lists.postgresql.org" References: Content-Language: de-DE, en-GB From: Jim Jones In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/02/2026 16:08, Fujii Masao wrote: > On Thu, Feb 12, 2026 at 11:36 PM Matheus Alcantara > wrote: >> The patch fix the issue and it seems correct to me. Thanks for the review! > 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. Hmm, it seemed so obvious to me that I didn’t look more closely at the documentation :) Although I struggle to see the rationale for not copying a table’s 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. What are your thoughts? Thanks! Best, Jim