| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | andres(at)anarazel(dot)de, masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-hackers(at)postgresql(dot)org, mmelihmutlu(at)gmail(dot)com |
| Subject: | Re: pg_stat_io for the startup process |
| Date: | 2023-04-26 12:34:05 |
| Message-ID: | CA+TgmoZt1oqrp6EyEV6_+QL8TLmvs_sEQr1wjC--jTHW1D3-+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 26, 2023 at 5:47 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> 3. When should we call pgstat_report_stats on the startup process?
>
> During recovery, I think we can call pgstat_report_stats() (or a
> subset of it) right before invoking WaitLatch and at segment
> boundaries.
I think this kind of idea is worth exploring. Andres mentioned timers,
but it seems to me that something where we just do it at certain
"convenient" points might be good enough and simpler. I'd much rather
have statistics that were up to date as of the last time we finished a
segment than have nothing at all.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-04-26 12:54:57 | Re: [PATCH] Infinite loop while acquiring new TOAST Oid |
| Previous Message | Daniel Gustafsson | 2023-04-26 12:31:38 | Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode |