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 1rV8Z9-00F53j-Mf for pgsql-docs@arkaria.postgresql.org; Wed, 31 Jan 2024 11:15:40 +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 1rV8Z8-00DYRe-Js for pgsql-docs@arkaria.postgresql.org; Wed, 31 Jan 2024 11:15:38 +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 1rV8Z8-00DYRW-CI for pgsql-docs@lists.postgresql.org; Wed, 31 Jan 2024 11:15:38 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rV8Z5-004hPg-GW for pgsql-docs@lists.postgresql.org; Wed, 31 Jan 2024 11:15:37 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 464775C010E; Wed, 31 Jan 2024 06:15:33 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 31 Jan 2024 06:15:33 -0500 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=1706699733; x=1706786133; bh=pVvCodyAmge+pnqo8lXM2p+ZS6jGaxyL ZQ9gHxk+54A=; b=dVAt1cb9XSoLBqjx7WtKt4YTf10JxEfyMQgbiYFVO5iy+b3y yEZoVcjJU4ASsSHnv8Ndg7dVGnemivpgqtX44wJaWlfPl0KPfzcdeml/A1f5+X0C iLIsks11j4koMjxM3g+gwsySTqseou5vBIr4770v8uPpvFoydyUeOAC4G8GwqsSH bxbkOA7b9JtqI/GKjhYMtKkoLAHIMsaYWj/iI9WCkAGzSzhpts9/ZAXEtGlNITE0 7wy5sS6+h93T+vhpBWMGoDL65CPJSSCsYa1B0vdm7l6ulr/qPzhuGb9MhUDHFTPa ADbmptFIx45DZ35No1ZKrnQPiVqEthdfRBZDVQ== 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=1706699733; x= 1706786133; bh=pVvCodyAmge+pnqo8lXM2p+ZS6jGaxyLZQ9gHxk+54A=; b=x rTtyiv7qV3H7z4yPJwXcxEJyHiEArLPW8qg44Hagkv6CydhyzNc4jQAVgNX3e9BI Jbngz7NwDGt0PIhU0xZjfI7+AULFlVZipRz0UFI++3r084XIW74CLdRShpGsGzvg X0Sw7+52j/tlpdE8oY9W+VR+6W4j3L7qJX3mQVyXbA1hbSbpdeWRe4x9fPY+yOU0 JBh3Taj2G73ptr6EYJtuZtBRO8yz5oxb3eBWfL22w0Dqg/ceDj6PkV/dCa6vQ4Um p1TzqWNllR1HUTsEsDgzMaUlQyELzwezxANxI0ABqLp3Trpa4JkhjRT0zO1VGLpC M0498sHAQdha1G8//HoEQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrfedtledgvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepjefhveehtdetgfffhffhfeefgffghffflefgieeuueek hedvhedvfeehffdvfeeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 31 Jan 2024 06:15:32 -0500 (EST) Message-ID: <1bcaae7c-a643-4e29-836a-974941941e91@eisentraut.org> Date: Wed, 31 Jan 2024 12:15:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: create table explicitly mention that unique|primary key constraint will create an Content-Language: en-US To: "David G. Johnston" Cc: Laurenz Albe , jian he , pgsql-docs@lists.postgresql.org References: <24f01200b651ff87311ae0f46b99eaf91fc3ec43.camel@cybertec.at> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 18.01.24 22:21, David G. Johnston wrote: > I started looking at this specific item and immediately got the idea to > actually document in user-facing (i.e., not system catalogs) what these > object categories are in which object types share the schema namespace. > The "Other Object Types" section already in the DDL chapter seems to > provide a near-perfect place to put this (not sure I like the word > "other" there being my only complaint).  The attached patch replaces > Laurenz's v1, leaving the create_table changes as-is but presenting an > alternative approach to introducing namespacing when we explain why > schemas exist. I think this proposal goes a bit too far into implementation-dependent details. The namespace of tables and indexes is clearly important, but for example, the subdivision of types into range types and multi-range types is really low-level and not usually practically relevant. And you don't mention array types, probably because they are not mentioned in typtype, but they are also relevant for the namespace of types. There are multiple ways to slice all this, but it's not clear why we need to lay this all out in the introductory documentation.