Re: Warning about using pg_stat_reset() and pg_stat_reset_shared()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Warning about using pg_stat_reset() and pg_stat_reset_shared()
Date: 2022-09-28 16:02:03
Message-ID: CA+TgmoY1giSdrAzrdFAi7jenkFV7jZ8rhx9Uwt3JBTxhxTowyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 28, 2022 at 11:45 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> We have discussed the problems caused by the use of pg_stat_reset() and
> pg_stat_reset_shared(), specifically the removal of information needed
> by autovacuum. I don't see these risks documented anywhere. Should we
> do that?

+1.

> Are there other risks?

I don't know.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Önder Kalacı 2022-09-28 16:08:41 A potential memory leak on Merge Join when Sort node is not below Materialize node
Previous Message Bruce Momjian 2022-09-28 15:44:59 Warning about using pg_stat_reset() and pg_stat_reset_shared()