Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kctQr-0006Bw-98 for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Nov 2020 16:57:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kctQq-00023m-7h for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Nov 2020 16:57:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kctQq-00023f-0h for pgsql-hackers@lists.postgresql.org; Wed, 11 Nov 2020 16:57:16 +0000 Received: from n3.nabble.com ([162.255.23.22]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kctQh-0004rN-VX for pgsql-hackers@postgresql.org; Wed, 11 Nov 2020 16:57:14 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 603FF229BF876 for ; Wed, 11 Nov 2020 09:57:06 -0700 (MST) Date: Wed, 11 Nov 2020 09:57:06 -0700 (MST) From: legrand legrand To: pgsql-hackers@postgresql.org Message-ID: <1605113826391-0.post@n3.nabble.com> In-Reply-To: <024ba056-6b4f-b26c-af17-297c1bbca65a@postgrespro.ru> References: <20200909092752.c91758a1bec3479668e82643@sraoss.co.jp> <20200917.094245.433560970731138050.t-ishii@sraoss.co.jp> <20201001033426.GB8130@paquier.xyz> <20201001.130351.116296702183559169.t-ishii@sraoss.co.jp> <497aa257-ecad-e439-39b3-944ab08d6fb9@oss.nttdata.com> <20201001140627.1f8fafe595f545e026d110c6@sraoss.co.jp> <20201005181618.31f2baf8583358fcfbed26cd@sraoss.co.jp> <024ba056-6b4f-b26c-af17-297c1bbca65a@postgrespro.ru> Subject: Re: Implementing Incremental View Maintenance 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 Hello Konstantin, I remember testing it with pg_stat_statements (and planning counters enabled). Maybe identifying internal queries associated with this (simple) test case, could help dev team ? Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html