| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CHECKPOINT unlogged data |
| Date: | 2025-05-30 17:07:48 |
| Message-ID: | aDnl5N1u7UBYVaSt@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 30, 2025 at 12:39:02PM -0400, Andres Freund wrote:
> On 2025-05-30 18:17:45 +0200, Christoph Berg wrote:
>> A customer reported to use CHECKPOINT before shutdowns to make the
>> shutdowns themselves faster and asked if it was possible to make
>> CHECKPOINT optionally also write out unlogged table data for that
>> purpose. I think the idea makes sense, so there's the patch.
>
> I've seen the need for this quite a few times, fwiw. So +1 to the idea.
This patch also adds an IMMEDIATE option, which I proposed some time ago
[0]. I ended up withdrawing it due to general skepticism about its
usefulness. FWIW I have no concerns about adding a few retail options to
CHECKPOINT, but others might balk at options without solid use-cases. The
unlogged table one seems reasonable enough.
[0] https://postgr.es/m/17A03557-CF5C-4D4B-B719-A1D98DD75E75%40amazon.com
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2025-05-30 17:23:04 | Re: CHECKPOINT unlogged data |
| Previous Message | Andres Freund | 2025-05-30 17:02:41 | Re: CHECKPOINT unlogged data |