MIME-Version: 1.0
References: <CAA5RZ0sQxAu6bU8wTgvs+aTSvhBcziH9jCJ27aS1hzKsm2kmTQ@mail.gmail.com>
 <CAHGQGwGBkPEK=NpLuk1HSmccu6OA2FYqkkGcA-Hb3WLs6dX=cg@mail.gmail.com>
 <aXHVC6NxERhcThZV@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAHGQGwHttst8tv_WWYNoGGfL1UAq4kiy6dpFXoxEkJwHMS9FtQ@mail.gmail.com>
 <aXJUK90lKXw3wrZn@ip-10-97-1-34.eu-west-3.compute.internal>
 <aXcQ0Bdff5OsUDWY@ip-10-97-1-34.eu-west-3.compute.internal>
 <aXmuKZz8sXPLCumT@paquier.xyz> <aXnveIxQEB5wwcB8@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0tGhu9jXGgFjzx7yK4cseE+t40Q4qZ+KhY66B2MZ=pBrQ@mail.gmail.com>
 <CAA5RZ0tvxZTZ7Xwm7FjWxAY_OphCq7tmpCaLgas0qrh+J86pRg@mail.gmail.com>
 <aYDb7g5hXnaP+5BU@ip-10-97-1-34.eu-west-3.compute.internal> <CAN4CZFOgx0steMN23afxauphppMzvBD3y7u8Oi6XV8Eg3D3m1Q@mail.gmail.com>
In-Reply-To: <CAN4CZFOgx0steMN23afxauphppMzvBD3y7u8Oi6XV8Eg3D3m1Q@mail.gmail.com>
From: Sami Imseih <samimseih@gmail.com>
Date: Wed, 4 Feb 2026 14:15:02 -0600
Message-ID: <CAA5RZ0vgts58i4M99q-zRdSiBiHMJ2p+c9S6sYqzWvsK6sSaGg@mail.gmail.com>
Subject: Re: Flush some statistics within running transactions
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Michael Paquier <michael@paquier.xyz>, 
	Fujii Masao <masao.fujii@gmail.com>, pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAA5RZ0vgts58i4M99q-zRdSiBiHMJ2p%2Bc9S6sYqzWvsK6sSaGg%40mail.gmail.com>
Precedence: bulk

>   do { \
> + pgstat_report_mixed_anytime = true; \
>   if (pgstat_should_count_relation(rel)) \
>   (rel)->pgstat_info->counts.numscans++; \
>
> Shouldn't these pgstat_report_mixed_anytime changes go inside the if
> statement in all macros?

I think you are correct here, and there is an even more fundamental issue.

since
``
#define pgstat_should_count_relation(rel) \
(likely((rel)->pgstat_info != NULL) ? true : \
```
could return if there is already a pgstat_info, we may never actually
enable the timeout.

so, I think we should:

1/

remove the scheduling of the timeout from pgstat_prep_pending_entry

@@ -1308,11 +1308,6 @@ pgstat_prep_pending_entry(PgStat_Kind kind, Oid
dboid, uint64 objid, bool *creat

                entry_ref->pending =
MemoryContextAllocZero(pgStatPendingContext, entrysize);
                dlist_push_tail(&pgStatPending, &entry_ref->pending_node);
-
-               /* Schedule next anytime stats update timeout */
-               if ((kind_info->flush_mode == FLUSH_ANYTIME ||
pgstat_report_mixed_anytime) &&
-                       IsUnderPostmaster &&
!get_timeout_active(ANYTIME_STATS_UPDATE_TIMEOUT))
-
enable_timeout_after(ANYTIME_STATS_UPDATE_TIMEOUT,
pgstat_flush_interval);
        }

2/

Create a routine to schedule the timeout:

+void
+ScheduleAnyTimeUpdate(void)
+{
+       /* Schedule next anytime stats update timeout */
+       if (IsUnderPostmaster &&
!get_timeout_active(ANYTIME_STATS_UPDATE_TIMEOUT))
+               enable_timeout_after(ANYTIME_STATS_UPDATE_TIMEOUT,
pgstat_flush_interval);
+
+       pgstat_report_mixed_anytime = true;
+}

This will also set pgstat_report_mixed_anytime to true. In my earlier
comments, I mentioned
having this as a public routine will be needed for extensions that
register a custom kind as well.

3/

All the count routines that wish to schedule any ANYTIME update because
their kind allows it can do so with ScheduleAnyTimeUpdate(). In the relation
stats, this can happen after it is checked that the relation should
track counts.

+#define pgstat_count_heap_scan(rel)                                 \
+    do {                                                            \
+        if (pgstat_should_count_relation(rel))                       \
+        {                                                           \
+            (rel)->pgstat_info->counts.numscans++;                   \
+            ScheduleAnyTimeUpdate();                                  \
+        }                                                           \
+    } while (0)


Also, it would be good to check if we have anytime flushes of either a mixed or
a fixed kind. Not strictly necessary, but I think it's better to avoid
needlessly entering
the flush routines.

@@ -2220,11 +2215,27 @@ pgstat_report_anytime_stat(bool force)

        pgstat_assert_is_up();
        /* Flush stats outside of transaction boundary */
-       pgstat_flush_pending_entries(nowait, true);
-       pgstat_flush_fixed_stats(nowait, true);
+       if (pgstat_report_mixed_anytime)
+               pgstat_flush_pending_entries(nowait, true);
+
+       if (pgstat_report_mixed_anytime)
+               pgstat_flush_fixed_stats(nowait, true);

        pgstat_report_mixed_anytime = false;
+       pgstat_report_fixed = false;
 }

I think we could benefit from a test that st track_counts to OFF inside
a transaction and re-enables it, to make sure the pgstat_should_count_relation
work is done correctly.

--
Sami Imseih
Amazon Web Services (AWS)