Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j9x4i-00064m-Rn for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Mar 2020 20:26:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j9x4f-0000gi-GQ for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Mar 2020 20:26:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j9x4f-0000gb-7p for pgsql-hackers@lists.postgresql.org; Thu, 05 Mar 2020 20:26:29 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1j9x4X-0003nO-3E for pgsql-hackers@postgresql.org; Thu, 05 Mar 2020 20:26:28 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 536431B7A049E for ; Thu, 5 Mar 2020 13:26:19 -0700 (MST) Date: Thu, 5 Mar 2020 13:26:19 -0700 (MST) From: legrand legrand To: pgsql-hackers@postgresql.org Message-ID: <1583439979339-0.post@n3.nabble.com> In-Reply-To: References: <1578237055901-0.post@n3.nabble.com> <1578247319224-0.post@n3.nabble.com> <1582902395847-0.post@n3.nabble.com> <1583074536018-0.post@n3.nabble.com> <1583150476569-0.post@n3.nabble.com> Subject: Re: Planning counters in pg_stat_statements (using pgss_store) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Never mind ... Please consider PG13 shortest path ;o) My one is parse->queryId != UINT64CONST(0) in pgss_planner_hook(). It fixes IVM problem (verified), and keep CTAS equal to pgss without planning counters (verified too). Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html