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 1rx4nX-006FJN-CR for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Apr 2024 12:54:00 +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 1rx4nU-00BFn1-Di for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Apr 2024 12:53:56 +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 1rx4nT-00BFms-E4 for pgsql-hackers@lists.postgresql.org; Wed, 17 Apr 2024 12:53:56 +0000 Received: from wfout1-smtp.messagingengine.com ([64.147.123.144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rx4nL-001Sau-TP for pgsql-hackers@lists.postgresql.org; Wed, 17 Apr 2024 12:53:54 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.west.internal (Postfix) with ESMTP id 3267B1C000C5; Wed, 17 Apr 2024 08:53:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 17 Apr 2024 08:53:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm2; t=1713358422; x=1713444822; bh=oFZT4BjkNQ0Z66Z7YFlff6CPMZkm8c2u 0JFAroj9dxw=; b=dd+xta213kvGUnPuS5SPNlxf+uODD/j73Lkuo5yBTY8pMutv sIf9rpo+CYtL/eFyG3R7znayakRfg8B9D5tak81MrcbBsG2Jn9QH/iLRQVhao25s uFyKmOW2XUQtB82N5+UjY6v+3g1mlW+fBLcVALFdnlCfbkuyosVj6hD8kRqfszBj bWadphEDnz9ynHf+0axeONVBvB7HHuFsowUbmL4gxxtgZMOjTjsTPsYMPQHMTyFJ oJd1AofISxntu8vVlc9o0NgmS2VQcUaVvdfyV008+skcTO7CJPFRAx90xfv2cTh9 mZd7/aIt3wUjgvVXEv8JbcLwCg5EwjcgqCmUyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1713358422; x= 1713444822; bh=oFZT4BjkNQ0Z66Z7YFlff6CPMZkm8c2u0JFAroj9dxw=; b=H S7utvxiEnYvmlFG8hIDI3NJwL/lMmQka46gp0oy3hQOGEwFJV6zfKPQvD9CIjdef BDVrX7gQ98O9NS6csylgpb7V5UftKo99ESBK5rn1CAq0lInjqQGk6zi2GKupzfxU QN2sgDCrHJ8RyNCla22+PYCoGNfWDe4U1p19rdPD/3nCggH4VO6P+ZvA6SApwG+P y8969jyW7U2SjXfosBv0kM8GEVuHAAM5X4ojADsa114yt/3iQJq5/Cvzc4ybY+bG XNwmEAz+T/CfzxOysBwOABHVqx4NzwpMzl6IWFMCl8hOvfcmpm9zjHfOBosYOGMA 1d2Bv2eU7ROsoOPOzFAsQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudejkedgheejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepgfejtdfhkeeftdeugfeileehteeljeeghfeuledthfeu tedvffdukeefjefhgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 17 Apr 2024 08:53:41 -0400 (EDT) Message-ID: <59ea426c-e31b-4b88-b970-eda808af9cc0@eisentraut.org> Date: Wed, 17 Apr 2024 14:53:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: CREATE TABLE creates a composite type corresponding to the table row, which is and is not there To: "David G. Johnston" , Erik Wienhold Cc: Hannu Krosing , PostgreSQL Hackers References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 29.03.24 02:42, David G. Johnston wrote: > We do use the term "stand-alone composite" in create type so I'm > inclined to use it instead of "composite created with CREATE TYPE"; > especially in the error messages; I'm a bit more willing to add the > cross-reference to create type in the user docs. I'm not sure this would have helped. If you see this in the error message, then there is no additional guidance what a "stand-alone composite type" and a not-"stand-alone composite type" are. Maybe it's possible to catch the forbidden cases more explicitly and come up with more helpful error messages along the lines of "cannot create a typed table based on the row type of another table".