Date: Sun, 3 Apr 2022 13:34:00 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Fujii Masao <fujii@postgresql.org>,
	Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
	melanieplageman@gmail.com
Subject: Re: Higher level questions around shared memory stats
Message-ID: <202204031134.5dbijyxdtzqx@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220403024548.ncy5civxjfqjnqad@alap3.anarazel.de>
Archived-At: <https://www.postgresql.org/message-id/202204031134.5dbijyxdtzqx%40alvherre.pgsql>
Precedence: bulk

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/