| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Planning counters in pg_stat_statements (using pgss_store) |
| Date: | 2020-04-09 04:00:03 |
| Message-ID: | 11032f50-104f-843b-715c-d83df9158aaf@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/04/08 21:32, legrand legrand wrote:
> Fujii Masao-4 wrote
>> On 2020/04/03 16:26
>> [...]
>>>
>>> "Note that planning and execution statistics are updated only at their
>>> respective end phase, and only for successful operations.
>>> For example the execution counters of a long running query
>>> will only be updated at the execution end, without showing any progress
>>> report before that.
>>
>> Probably since this is not the example for explaining the relationship of
>> planning and execution stats, it's better to explain this separately or
>> just
>> drop it?
>>
>> What about the attached patch based on your proposals?
>
> +1
> Your patch is perfect ;^>
Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2020-04-09 04:14:24 | Re: A problem about partitionwise join |
| Previous Message | Fujii Masao | 2020-04-09 03:59:43 | Re: Planning counters in pg_stat_statements (using pgss_store) |