Re: Flush some statistics within running transactions

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Flush some statistics within running transactions
Date: 2026-01-27 16:53:41
Message-ID: CAA5RZ0uAMqEurSwO=FUzZf5BnamEDoN04W-uuLnY6oWdMchicg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Some statistics are updated while a transaction is in progress (this includes
> blks_read, blks_hit, tup_returned and tup_fetched).

I am ok with this. Just a slight change.

"""
Some statistics are updated while a transaction is in progress
(for example, blks_read, blks_hit, tup_returned, and tup_fetched).
"""

The difference is "for example" makes it clear this is not a comprehensive list.

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-01-27 17:02:59 Re: unnecessary executor overheads around seqscans
Previous Message Greg Burd 2026-01-27 16:53:38 Re: pgsql: Prevent invalidation of newly synced replication slots.