| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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-02-04 16:26:35 |
| Message-ID: | CAA5RZ0sqJzpBZnOY3rOy5x7+WL_UDnoMkn2S_ZoXPPOWZkXSbA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Will address below in the comments.
Sorry there was one more comment I forgot about.
in v5-0004, instead of `flush_anytime_cb`, can't we
just pass the anytime flag to the `flush_pending_cb` and
take care of what needs to be flushed there?
It will be up to the author of the kind if they want to further
split work in multiple functions, but we could just have a
single callback that is ANYTIME aware.
--
Sami Imseih
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-02-04 16:42:59 | Re: Pasword expiration warning |
| Previous Message | Fujii Masao | 2026-02-04 16:20:51 | Re: Add --system-identifier / -s option to pg_resetwal |