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 1jQrDR-0006fU-61 for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Apr 2020 11:37:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jQrDO-0000Qo-UY for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Apr 2020 11:37:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jQrDO-0000Qg-OS for pgsql-bugs@lists.postgresql.org; Tue, 21 Apr 2020 11:37:22 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jQrDF-0001Qh-Pl for pgsql-bugs@postgresql.org; Tue, 21 Apr 2020 11:37:20 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 51BBE1CBB648F for ; Tue, 21 Apr 2020 04:37:12 -0700 (MST) Date: Tue, 21 Apr 2020 04:37:12 -0700 (MST) From: legrand legrand To: pgsql-bugs@postgresql.org Message-ID: <1587469032291-0.post@n3.nabble.com> In-Reply-To: <54fa2fec-b133-0fc0-4227-3e308ba68812@oss.nttdata.com> References: <1584293755198-0.post@n3.nabble.com> <1585330995153-0.post@n3.nabble.com> <54fa2fec-b133-0fc0-4227-3e308ba68812@oss.nttdata.com> Subject: Re: pg_stat_statements: rows not updated for CREATE TABLE AS SELECT statements 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 Fujii Masao-4 wrote > Attached is the patch that makes pgss track the total number of rows > retrieved or affected by CREATE TABLE AS, SELECT INTO, > CREATE MATERIALIZED VIEW and FETCH. I think this is new feature > rather than bug fix, so am planning to add this patch into next CommitFest > for v14. Thought? Thanks ! maybe v13, if this was considered as a bug that don't need backport ? Regards PAscal -- Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html