Re: Proposal: Limitations of palloc inside checkpointer

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Maxim Orlov <orlovmg(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Ekaterina Sokolova <e(dot)sokolova(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Limitations of palloc inside checkpointer
Date: 2025-08-07 07:16:58
Message-ID: CABPTF7XWmbSFARP0WQsUUxXbq138QZz7MqHLZJb-3TNCse2_sg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Tom!

Thanks for catching this.

On Thu, Aug 7, 2025 at 2:58 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> > I'm going to push this if no objections.
>
> I looked at these patches while preparing release notes, and
> found an oversight. CheckpointerShmemInit does
>
> CheckpointerShmem->max_requests = Min(NBuffers, MAX_CHECKPOINT_REQUESTS);
>
> but CheckpointerShmemSize still does
>
> size = add_size(size, mul_size(NBuffers, sizeof(CheckpointerRequest)));
>
> So if NBuffers is more than MAX_CHECKPOINT_REQUESTS, we will allocate
> extra CheckpointerRequest array entries that we will never use,
> wasting shared memory. Admittedly the amount is small relative to the
> shared buffers themselves, but at the very least this is confusing.
>
> The comment in CheckpointerShmemSize needs adjustment, too.

I attached a patch to fix it.

Best,
Xuneng

Attachment Content-Type Size
v1-0001-Fix-checkpointer-shared-memory-allocation.patch application/octet-stream 1.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-08-07 07:17:29 Re: BF mamba failure
Previous Message shveta malik 2025-08-07 06:55:04 Re: Proposal: Conflict log history table for Logical Replication