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 1qisXK-0089YF-DM for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Sep 2023 08:26:18 +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 1qisXI-00FM4a-PO for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Sep 2023 08:26:16 +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 1qisXI-00FM4I-GE for pgsql-bugs@lists.postgresql.org; Wed, 20 Sep 2023 08:26:16 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qisXF-005ajD-EE for pgsql-bugs@lists.postgresql.org; Wed, 20 Sep 2023 08:26:15 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 4AEE5320090A; Wed, 20 Sep 2023 04:26:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 20 Sep 2023 04:26:11 -0400 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:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1695198370; x=1695284770; bh=Q Zr9l9+mVqt6UodjB8y4shcpt2nZcVBAiC5R65qvDOg=; b=T09Y7LWFxQo93qAh2 ok3/qOyXhv7foiOUo5/ep0CaBk3krX/RoYfUJbaLhFSVEpBT2tmePNZA34VXHb3M YYovv2z1Lp5hAT4apz8aYSLs8tzCIDD03YNR51y9qxdbHKNfFXWo9lyLUU7izPIo +L//TLV6kZWlkEZMprvygAUjs7qo1xK4K/iWntdAGWuI7S0KCfWszGCbx7DHf2IO TUTTa3QGz+9EX5NU6QQ/nqGG+yTDmhy++2lxwj7qW4YpXym3V4xQAUV3e1My+wqN AQ0XBsbmKH7woMqTESoCCmGdpLDqubbQdzKApJDbT5s8Va5BGU/bXqMmcso3S+Xd Ld0Dg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudekfedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugfgjgesthekre dttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepudejveejffejve duudetvdekieeuiedtvdeileefkeevjedufeeguedvjefhueelnecuffhomhgrihhnpegv nhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 20 Sep 2023 04:26:10 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id CFA6DC5; Wed, 20 Sep 2023 10:26:07 +0200 (CEST) Date: Wed, 20 Sep 2023 10:26:07 +0200 From: Alvaro Herrera To: bchen90@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18112: pgstattuple of sequence failed Message-ID: <202309200826.z3ckjb4g7auj@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <18112-724de41f491c9878@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Sep-15, PG Bug reporting form wrote: > I found pgstattuple of sequence will be failed but not PG11.x, for the code > of pgstattuple it looks like still support of sequence, but the > "rel->rd_rel->relam now is 0, not HEAP_TABLE_AM_OID", so the error report > > postgres=# select pgstattuple('test'); > ERROR: SQLSTATE 0A000: only heap AM is supported OK, but so what? I mean, what useful information are you extracting using pgstattuple from a sequence? What decisions can you make based on these results? -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "We're here to devour each other alive" (Hobbes)