Hi,
However, as you said, for most use cases, pg_stat_statements and
log_statement may be sufficient.
I would like to withdraw this proposal.
Well, they either require extensions or parameters to be set properly.
One advantage I see to store those kind of information is that it can be
queri
On Tue, Sep 07, 2021 at 06:11:14PM +0900, Seino Yuki wrote:
> I would like to withdraw this proposal.
This was registered in the CF, so marked as RwF.
--
Michael
signature.asc
Description: PGP signature
On 2021-09-01 23:15, Fujii Masao wrote:
Why do you want to treat only REFRESH MATERIALIZED VIEW command
special?
What about other utility commands like TRUNCATE, CLUSTER, etc?
First of all, knowing the update date and time of the MATVIEW is
essential for actual operation.
Without that inform
On 2021/07/09 1:39, Seino Yuki wrote:
Hi.
This is a proposal for a new feature in statistics collector.
I think we need to add statistics about refresh matview to pg_stat_all_tables
view.
Why do you want to treat only REFRESH MATERIALIZED VIEW command special?
What about other utility comm
Hi.
This is a proposal for a new feature in statistics collector.
I think we need to add statistics about refresh matview to
pg_stat_all_tables view.
When the "REFRESH MATERIALIZED VIEW" was executed, the number of times
it was executed
and date it took were not recorded anywhere.
"pg_stat_
