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.94.2) (envelope-from ) id 1r8MTR-009TmX-74 for pgsql-docs@arkaria.postgresql.org; Wed, 29 Nov 2023 15:27:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r8MTP-00BTjF-ND for pgsql-docs@arkaria.postgresql.org; Wed, 29 Nov 2023 15:27:35 +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.94.2) (envelope-from ) id 1r8MTN-00BTj7-Qj for pgsql-docs@lists.postgresql.org; Wed, 29 Nov 2023 15:27:35 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8MTJ-009Bto-G5 for pgsql-docs@lists.postgresql.org; Wed, 29 Nov 2023 15:27:32 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 636DA5C0345; Wed, 29 Nov 2023 10:27:26 -0500 (EST) Received: from imap49 ([10.202.2.99]) by compute2.internal (MEProxy); Wed, 29 Nov 2023 10:27:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1701271646; x=1701358046; bh=s3 03XBfyGkVgp3/RvaZaAQTjvqOebgjjTWHCgpcbQUY=; b=s+h+iLrEhgFSJxt1YY 8XyKdxAeg3apvUR+IaK0jbrVzOilRLyVEm0vGfEDEkjKTgjdhJ/SZJdR6TPw6O/Z 9/kQ4+knJ6Ob+mr1GTzU5Vu9uKOSxKPRfgrf1JskmDAohVANO0ALObocwCrs6utM jjquPihx3rYm/7xjzC/whTDKYtxZn1vTH/AiLe+QtCjQLAVPHxrcRs8wCAXAwK7A eYiflgx88/pABfQNEXQfWpxJUEUiwdBxxal9UA4xyVW00MS4cvHE20EmLDXU14hn EIOJ13Sl/IMv+Xga6HD/gsZ07UnIe5HTyV67xEBXS62lZToso7S3mUuMaDyh/lJE hI4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1701271646; x=1701358046; bh=s303XBfyGkVgp 3/RvaZaAQTjvqOebgjjTWHCgpcbQUY=; b=CUHOJXqlZ3kL5iKxjbcRSkii9IETQ KoMc7jf8iNj7O2FDLFLLlHxkKuWllAiHFNvYb5z3897w9B1ivOC3Ae9Hb30B0KuJ eIP/z+HdqSxZaBcMYUx8DAg+/eAJuU3H/l90r/LWRn04T2v/qr+RMIYBSBGqT41p Ginh9pzxde0rz/91BFQg6vSxdpz1qArRMkEh0bFSzLhildqjCZSRuNX3/p47u5Nx HB97Rct2hh3g2g4qYrdUe1klbYu2S+ssPtIrHvNvdCk7JeKmAOmRK3uSD2jFt1vc MuRvUNTTpQKjqPaQBuRvs0aOYeievta8M1zOMuJL+Qnn1p/r3eBdsDDDg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeihedgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfgfhulhgvrhcuvfgrvhgvihhrrgdfuceovghulhgvrhes vghulhgvrhhtohdrtghomheqnecuggftrfgrthhtvghrnhepjeethfeuvdfgffdtteevud eftdejueffkeelveekhfevkeegleefhfejhedtjeegnecuffhomhgrihhnpegvnhhtvghr phhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegvuhhlvghrsegvuhhlvghrthhordgtohhm X-ME-Proxy: Feedback-ID: i0c21471d:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 01CEC15A0092; Wed, 29 Nov 2023 10:27:25 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1234-gac66594aae-fm-20231122.001-gac66594a MIME-Version: 1.0 Message-Id: In-Reply-To: <170109752554.398199.1576920096317923086@wrigleys.postgresql.org> References: <170109752554.398199.1576920096317923086@wrigleys.postgresql.org> Date: Wed, 29 Nov 2023 12:24:23 -0300 From: "Euler Taveira" To: david@robbez.com, pgsql-docs@lists.postgresql.org Subject: Re: Clarification regarding CREATE TABLE LIKE and FOREIGN KEYS Content-Type: multipart/alternative; boundary=54f4e653805a4858bcedc11e6938c8bf List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --54f4e653805a4858bcedc11e6938c8bf Content-Type: text/plain On Mon, Nov 27, 2023, at 12:05 PM, PG Doc comments form wrote: > It is not clear to me that foreign keys are copied or not when duplicating a > table using CREATE TABLE ... LIKE ... INCLUDING ALL. I had to actually test > to check what it does. > It is impractical to add what a feature *does not* provide in general. The probability that that information will be obsolete (due to new features) is high. If the information is missing that's because it is not supported. (Of course, it can be an omission and, in this case, we need to fix it.) -- Euler Taveira EDB https://www.enterprisedb.com/ --54f4e653805a4858bcedc11e6938c8bf Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Mon, Nov 27,= 2023, at 12:05 PM, PG Doc comments form wrote:
It is not clear to me that foreign = keys are copied or not when duplicating a
table using CREA= TE TABLE ... LIKE ... INCLUDING ALL. I had to actually test
to check what it does.


<= /div>
It is impractical to add what a feature *does not* provide in = general. The
probability that that information will be obs= olete (due to new features) is
high. If the information is= missing that's because it is not supported. (Of
course, i= t can be an omission and, in this case, we need to fix it.)


--
Euler Taveira

--54f4e653805a4858bcedc11e6938c8bf--