Re: [PATCH] Add features to pg_stat_statements - Mailing list pgsql-hackers

From Katsuragi Yuta
Subject Re: [PATCH] Add features to pg_stat_statements
Date
Msg-id dcb63417e592d5966c19c04f90db0aef@oss.nttdata.com
Whole thread Raw
In response to Re: [PATCH] Add features to pg_stat_statements  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: [PATCH] Add features to pg_stat_statements  (Yuki Seino <seinoyu@oss.nttdata.com>)
List pgsql-hackers
On 2020-09-24 18:55, legrand legrand wrote:
> Not limited to 3, Like an history table.
> 
> Will have to think if data is saved at shutdown.

Thanks.

This design might introduce some additional complexity
and things to be considered.
For example, the maximum size of "history table",
how to evict entries from the history table and how to manage
the information maintained by evicted entries.

Also, providing a history table looks similar to logging.

Providing the original view (# of dealloc and last_dealloc ts)
and optional logging looks a simple and better way.

Regards,
Katsuragi Yuta



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: vs formatting in the docs
Next
From: Peter Eisentraut
Date:
Subject: Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration