Re: May be BUG. Periodic burst growth of the checkpoint_req counter on replica.

From: "Anton A(dot) Melnikov" <aamelnikov(at)inbox(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: May be BUG. Periodic burst growth of the checkpoint_req counter on replica.
Date: 2023-03-16 12:39:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 15.03.2023 21:29, Gregory Stark (as CFM) wrote:

> These patches that are "Needs Review" and have received no comments at
> all since before March 1st are these. If your patch is amongst this
> list I would suggest any of:
> 1) Move it yourself to the next CF (or withdraw it)
> 2) Post to the list with any pending questions asking for specific
> feedback -- it's much more likely to get feedback than just a generic
> "here's a patch plz review"...
> 3) Mark it Ready for Committer and possibly post explaining the
> resolution to any earlier questions to make it easier for a committer
> to understand the state

There are two different patch variants and some discussion expected.
So moved them to the next CF.

With the best wishes!

Anton A. Melnikov
Postgres Professional:
The Russian Postgres Company

Attachment Content-Type Size
v3-0001-Fix-burst-checkpoint_req-growth.patch text/x-patch 2.4 KB
v2-0001-Add-restartpoint-stats.patch text/x-patch 8.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Zubkov 2023-03-16 12:39:24 Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Previous Message Amit Kapila 2023-03-16 12:25:22 Re: Data is copied twice when specifying both child and parent table in publication