Re: Proposal: Limitations of palloc inside checkpointer

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Ekaterina Sokolova <e(dot)sokolova(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal: Limitations of palloc inside checkpointer
Date: 2025-02-28 08:55:45
Message-ID: CACG=ezbQrdr8orTXnu6_kWpJ_VC1MEm7Y89ACMVBB0mm+zCROA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here is an alternative solution. We can limit the number of processed
requests to fit in a 1Gb memory chunk for each pass. Obviously, we left
some requests in the queue to be processed in the next call. We can
overcome this by using multi-step processing: estimating the number of
steps in the beginning and processing requests again.

I'd like to hear your opinion on the subject.

--
Best regards,
Maxim Orlov.

Attachment Content-Type Size
v3-0001-Limit-AbsorbSyncRequests-to-1Gb-at-once.patch application/octet-stream 1.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-02-28 09:21:29 Re: Statistics Import and Export: difference in statistics dumped
Previous Message Michael Paquier 2025-02-28 08:44:20 Re: [BUG]: the walsender does not update its IO statistics until it exits