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 1rV7h4-00EzKM-6Q for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jan 2024 10:19:47 +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 1rV7h3-00DGc5-7T for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jan 2024 10:19:45 +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.94.2) (envelope-from ) id 1rV7h2-00DGbx-K7 for pgsql-bugs@lists.postgresql.org; Wed, 31 Jan 2024 10:19:44 +0000 Received: from fout1-smtp.messagingengine.com ([103.168.172.144]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rV7gu-004JAS-Tz for pgsql-bugs@lists.postgresql.org; Wed, 31 Jan 2024 10:19:42 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfout.nyi.internal (Postfix) with ESMTP id 580F5138006A; Wed, 31 Jan 2024 05:19:36 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 31 Jan 2024 05:19:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:reply-to :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1706696376; x=1706782776; bh=V CCbc1hTA8DVUlh/xc8c2zgIHwr/tvMF1G8Q8NiGfaI=; b=EN05G6uU2CCIFAlC1 frA6Y775YmTqQu/Qw9gRZBL727y4KQ/Wc30pTdiZVBMFaZ27kneU15Kh6ejth9GC xOWzkgQ+4EkdSVjHwzkpnQTHqKiIX3Bypz264ySe4Ho4Ir0k7U5FYl769agV1R4R RB00GAFG0ipvzYBOo5bWT7w1h0Nj0/JdFzyYFLtjEKe0cLrK86ePYX71+ODGaqZZ 7mc6rJBJypIvU/64eOsw9yrtrVbnLNPJ0BFprAETvwHErEd1SbIyxfMEUxpQPlC/ RVFZjqlAhVkY73DBJSdslL8W7y61PhaoMGUQImhFZTZ82lM59+g1t2HLcrVTZeyc pVvkw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrfedtledgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugfgjgesthekre dttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepudejveejffejve duudetvdekieeuiedtvdeileefkeevjedufeeguedvjefhueelnecuffhomhgrihhnpegv nhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 31 Jan 2024 05:19:35 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1706696373; bh=YLltUfcA00mdzkfQGMRkpSHDrQt7YKbm3Hrfm0UQI8Q=; h=Date:From:To:Subject:In-Reply-To:From; b=XPAv8hB7UtggBsKy9u5i3KmZQ/oTD7193Smwa5HIM/lQilXlPjJI7f09QbWYqyFGz gMZ37BAJFoRR1KSHOzhIisIg0JQMyWRSd8cW557liQ1IeTT9YRfRXn8ivsr61JD5wS ag5oES/dX28pG6rdnRSp9sGqwLFBOtY9afFi0c4xL1mVzZF5m+odXKg8/KBfbkV56J W2Wpd9hYti2OpcTxL/gyuCFLqWQwzHqYXuqlpA01nIaYgclOilHY8DuMVc9/aymLBv xC1YKv/HAkZqo9Py+zA5I9icpf/yHo+LtK/n/00LuhubPUfUQ/vTAey6ZoSfnlHyC9 M8+xbDwel1Afw== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 1B3748B; Wed, 31 Jan 2024 11:19:33 +0100 (CET) Date: Wed, 31 Jan 2024 11:19:33 +0100 From: Alvaro Herrera To: 865229936@qq.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18316: The descriptions of the objoid and classoid fields in the pg_description section, include: 12,14,16 Message-ID: <202401311019.tks4hnuzi7dd@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <18316-9fce4e053fd270dc@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-Jan-31, PG Bug reporting form wrote: > The descriptions of the objoid and classoid fields in the documentation's > pg_description section are misunderstood. The description for objoid should > reference pg_class.oid, and the description for classoid should specify the > OID of pg_class, rather than "pg_class.oid." Hmm, no, that's not right. classid is supposed to refer to the pg_class.oid value of the object type being commented on -- if you comment on a table/view/etc then it's going to be the OID of pg_class. But if you comment on a function, it's going to be the OID of pg_proc, and so on. As for objoid, that one is going to refer to the OID of the object being commented on -- again, pg_class.oid if you are commenting on a table/view/etc, but it could be pg_proc.oid if you're commenting on a function, etc. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "¿Cómo puedes confiar en algo que pagas y que no ves, y no confiar en algo que te dan y te lo muestran?" (Germán Poo)