Re: Make use of assign_checkpoint_completion_target() to calculate CheckPointSegments correctly - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Make use of assign_checkpoint_completion_target() to calculate CheckPointSegments correctly
Date
Msg-id CALj2ACXvmygSJtLFViCdp=wi2nwJLRum5Cn-7Zvq=gEXwrGenw@mail.gmail.com
Whole thread Raw
In response to Re: Make use of assign_checkpoint_completion_target() to calculate CheckPointSegments correctly  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Make use of assign_checkpoint_completion_target() to calculate CheckPointSegments correctly
List pgsql-hackers
On Tue, Jan 17, 2023 at 12:31 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Dec 26, 2022 at 06:12:34PM +0530, Bharath Rupireddy wrote:
> > It looks like assign_checkpoint_completion_target() is defined [1],
> > but never used, because of which CheckPointSegments may miss to
> > account for changed checkpoint_completion_target. I'm attaching a tiny
> > patch to fix this.
> >
> > Thoughts?
>
> Oops.  It looks like you are right here.  This would impact the
> calculation of CheckPointSegments on reload when
> checkpoint_completion_target is updated.  This is wrong since we've
> switched to max_wal_size as of 88e9823, so this had better be
> backpatched all the way down.
>
> Thoughts?

+1 to backpatch as setting checkpoint_completion_target will not take
effect immediately.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Dag Lem
Date:
Subject: Re: daitch_mokotoff module
Next
From: Masahiko Sawada
Date:
Subject: Re: Perform streaming logical transactions by background workers and parallel apply