Re: Higher level questions around shared memory stats

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Fujii Masao <fujii(at)postgresql(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, melanieplageman(at)gmail(dot)com
Subject: Re: Higher level questions around shared memory stats
Date: 2022-04-03 11:34:00
Message-ID: 202204031134.5dbijyxdtzqx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Apr-02, Andres Freund wrote:

> 6) Should any part of the "reuse_stats" logic in table_recheck_autovac() be
> kept?
>
> With the shared memory stats patch, autovacuum can cheaply access individual
> stats, so the whole scheme for avoiding stats accesses is moot.

Agreed, I don't think there's need to keep any of that.

> I don't really see a point in keeping any of it - but I was curious whether
> anybody else does?

I don't either.

> I'm still polishing, so I didn't want to send a whole new version with these
> adjustments to the list yet, but you can see the state as of the time of
> sending this email at [1].

I'll have a look, thanks.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2022-04-03 11:44:36 Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Previous Message Alvaro Herrera 2022-04-03 11:21:56 Re: generic plans and "initial" pruning