MIME-Version: 1.0
References: <aYXL6XmVABORjGF5@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0tK=-Dukr4ofmKpPSK4-LwqrGXmzkqGoMuJKPXnGW3=AA@mail.gmail.com>
 <aZLVDJLTiFlxsWZi@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0tPsU_bCATn-Wtf8hMaKmrCwfxtLcY9Pp3NQPpLrH2G_Q@mail.gmail.com>
 <aZQTCJJm61J/X4nC@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0vDh+vbE5SY-+azQBxEhXrywaXGrK_Qn8DKEBwNsrDH_Q@mail.gmail.com>
 <aZVQ3nT9B6ti8whJ@ip-10-97-1-34.eu-west-3.compute.internal>
 <aZaKVOrRO_bHsevn@paquier.xyz> <aZbDYMrOkeCyIubO@ip-10-97-1-34.eu-west-3.compute.internal>
 <aZznT84Ssh8PywcH@paquier.xyz> <aZ2t5IZ2c7HBuDS3@ip-10-97-1-34.eu-west-3.compute.internal>
In-Reply-To: <aZ2t5IZ2c7HBuDS3@ip-10-97-1-34.eu-west-3.compute.internal>
From: Sami Imseih <samimseih@gmail.com>
Date: Tue, 24 Feb 2026 10:32:43 -0600
Message-ID: <CAA5RZ0uJvCH1U47+m8eCW_NHv+F8W484MBDLw_kc6AfLY74xTw@mail.gmail.com>
Subject: Re: Flush some statistics within running transactions
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Fujii Masao <masao.fujii@gmail.com>, 
	pgsql-hackers@lists.postgresql.org, Zsolt Parragi <zsolt.parragi@percona.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAA5RZ0uJvCH1U47%2Bm8eCW_NHv%2BF8W484MBDLw_kc6AfLY74xTw%40mail.gmail.com>
Precedence: bulk

> > 2) The need for all the stats to call pgstat_schedule_anytime_update()
> > in strategical places.  This is less of a burden compared to 1), but
> > this leads to more complications in these code paths with the coding
> > requirements, especially for custom stats kinds.
>
> I think that's solved with Sami's proposal for variable stats kind (to flush or
> schedule when the session is idle).

Just a clarification. It is "to schedule a flush when the transaction
becomes idle"
PGSTAT_IDLE_INTERVAL already deals when the session is idle.

--
Sami Imseih
Amazon Web Services (AWS)