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 1w5KRI-0038Zh-1O for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Mar 2026 09:22:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w5KRF-00DPsl-1z for pgsql-hackers@arkaria.postgresql.org; Wed, 25 Mar 2026 09:22:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w5KRF-00DPsb-14 for pgsql-hackers@lists.postgresql.org; Wed, 25 Mar 2026 09:22:09 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w5KRD-00000000wV1-1T1g for pgsql-hackers@lists.postgresql.org; Wed, 25 Mar 2026 09:22: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=1774430528; x=1805966528; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=XbVq0gLzuf802DYDLYJsBvEpgdfyq5MnhvQneufijXQ=; b=gTnjjweLEmmqlcSz3JubpZVotU8dX2iw7JkDrmcbS7TEAZGiV111iI6u pcIb+GNPtKezfyRnQLchlzN3tPsHQjB7t2WIC9qoXPbPVkO3y1nXUS1S6 GedmI3fDZ61YMWlLfrhxoRs6bsjNUrt9bU5GC0MdW4bHixEdxNfd4e6/+ 0/nekeqq+I8ANZvVq/nO9fDX3hiRrZtSom5MvyrIzyF7035olCEW1XFaI 76y3ACLCj7HC4VyPiPTaujDZywYnmkZiIPLBZlT0YDq8Udw8SDDxUS8/h fwWHKdFW+XqQq4ufiAcnkkjnjUsHdBsljAgbIa/HtdNefXHlJtO+WoN0D g==; X-CSE-ConnectionGUID: v9w23ylCQoW1x9rP7cZNgw== X-CSE-MsgGUID: qi3tf1PiTv6tneMF9nX4TA== X-IronPort-AV: E=Sophos;i="6.23,139,1770591600"; d="scan'208";a="388730634" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 25 Mar 2026 10:22:02 +0100 Received: from [192.168.178.27] (dynamic-093-131-238-209.93.131.pool.telefonica.de [93.131.238.209]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id D52BD20ADF0D; Wed, 25 Mar 2026 10:21:56 +0100 (CET) Message-ID: Date: Wed, 25 Mar 2026 10:21:56 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: COMMENTS are not being copied in CREATE TABLE LIKE To: Carlos Alves Cc: Tom Lane , Chao Li , Fujii Masao , Matheus Alcantara , "pgsql-hackers@lists.postgresql.org" , "David G. Johnston" References: <50f693ad-faec-4b1b-8de5-88dc90b236b4@uni-muenster.de> <421633.1770957043@sss.pgh.pa.us> <5888209c-44b5-438a-abd3-7d07990b3a4c@uni-muenster.de> Content-Language: de-DE, en-GB From: Jim Jones In-Reply-To: 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 24/03/2026 19:32, Carlos Alves wrote: > Just one point I'd like to address is the documentation. Following the > idea of the other "includings" options wouldn't it be interesting to > present a more concise text? As a suggestion, it could be something like: > > "Comments on columns, not null and check constraints, indexes, extended > statistics and the table itself from a source table will be copied. If > the command references multiple source tables with including clauses, > any existing table-level comments will be merged into a single entry, > separated by newlines in the order they were specified." In the second paragraph of the INCLUDING COMMENTS docs I wrote: If multiple LIKE clauses specify INCLUDING COMMENTS and the source tables have table-level comments, these comments will be concatenated in the new table, separated by newlines, in the order that the LIKE clauses appear. Which pretty much states the same? Please let me know if I am missing your point here. > I've attached some preliminary tests I performed. Thanks for the thorough tests. Much appreciated! Best, Jim