Re: [PATCH] Add features to pg_stat_statements

From: Katsuragi Yuta <btkatsuragiyu(at)oss(dot)nttdata(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Add features to pg_stat_statements
Date: 2020-09-25 05:46:00
Message-ID: dcb63417e592d5966c19c04f90db0aef@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-09-25 05:52:10 Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration
Previous Message Peter Eisentraut 2020-09-25 05:38:56 Re: <xref> vs <command> formatting in the docs