Subject: Re: pg_stat_statements: rows not updated for CREATE TABLE AS SELECT
 statements
To: legrand legrand <legrand_legrand@hotmail.com>, pgsql-bugs@postgresql.org
References: <1584293755198-0.post@n3.nabble.com>
 <c9463107-d605-9d9e-54e5-f065f2fc3c1f@oss.nttdata.com>
 <1585330995153-0.post@n3.nabble.com>
 <54fa2fec-b133-0fc0-4227-3e308ba68812@oss.nttdata.com>
 <1587469032291-0.post@n3.nabble.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
Message-ID: <f027b6ee-be9a-0774-14e3-59ef954c84f0@oss.nttdata.com>
Date: Wed, 22 Apr 2020 12:17:11 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
 Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <1587469032291-0.post@n3.nabble.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2020/04/21 20:37, legrand legrand wrote:
> 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 ?

Yeah, if many people think this is a bug, we can get it into v13.
But at least for me it looks like an improvement of the capability
of pgss rather than a bug fix. If the document of pgss clearly
explained "pgss tracks the total number of rows affect by even
utility command ...", I think that we can treat this as a bug. But...

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION