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 1w5pBj-003fSt-0R for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Mar 2026 18:12:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w5pBg-004Uka-1N for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Mar 2026 18:12:08 +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 1w5pBg-004UkP-0S for pgsql-hackers@lists.postgresql.org; Thu, 26 Mar 2026 18:12:08 +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 1w5pBe-00000001KYv-0JL2 for pgsql-hackers@lists.postgresql.org; Thu, 26 Mar 2026 18:12:08 +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=1774548727; x=1806084727; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=uJIlS1HB5ed3CIOUr9O4akdxtxL5YHKXFQvO6DrZK68=; b=k7+rDDuJUpZ6bYdlLDOBKxhHeMgM0iDzTgRFdmeZGvoB2bjsQuHqFuPv EliZpVjvMDynrLJTEIvtJ/WaPrATquOVVc1Si4ycOK9QLNDPBz0rgkNyF BYTxAvwBd7KVhHgZXdr8Ls85h45mzTSYl8eSxuNz4W/bFicQhCAk+E9MX Ho7VPEeck3YRPq6vAd1yMhHGIMXz5Iee9yDUcQUvpZe8RKl/hdc04KzNF oqSXus9bF0Kn2djDqKzw7Ubehk3zD2PBqr10rGwHMeMGeUwSH3ujUsU3l XJTY3csc9olu8lQVnlMGeWu8mkfXbG62KzWdhl1h9w2KihDYiEtbd9GDd Q==; X-CSE-ConnectionGUID: 7OpPgkGXSKqA1f0geMgTzA== X-CSE-MsgGUID: sg73ii5yTgm7atbuae64Og== X-IronPort-AV: E=Sophos;i="6.23,142,1770591600"; d="scan'208";a="388941385" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 26 Mar 2026 19:12:06 +0100 Received: from [192.168.178.27] (dynamic-093-133-025-145.93.133.pool.telefonica.de [93.133.25.145]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id 1407C20ADF02; Thu, 26 Mar 2026 19:12:05 +0100 (CET) Message-ID: Date: Thu, 26 Mar 2026 19:12:04 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE To: Carlos Alves , pgsql-hackers@lists.postgresql.org References: <177454798496.946.17517925915684610719.pgcf@coridan.postgresql.org> Content-Language: de-DE, en-GB From: Jim Jones In-Reply-To: <177454798496.946.17517925915684610719.pgcf@coridan.postgresql.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Carlos On 26/03/2026 18:59, Carlos Alves wrote: > No errors or failures were detected during the tests. > > The only suggestion is to keep the parameter description a single paragraph, following the same style as the description of the other inclusion parameters. But the current description is coherent and okay. > > After the tests, the patch is working as expected: > - Table-level comments are copied when the `including comments` parameter is used. > - When there is more than one source table, comments, if any, are kept in the order in which they appear in the command, separated by a new line. > - The performance of command execution was not affected. > > I think only the code review is missing, but I don't have much experience to perform this step. Thanks for this thorough review. This helps a lot! Let's see what the other reviewers have to say about the code and your docs suggestion. Best, Jim