Re: CHECKPOINT unlogged data

Christoph Berg <myon@debian.org>

From: Christoph Berg <myon@debian.org>

To: Nathan Bossart <nathandbossart@gmail.com>

Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Fujii Masao <masao.fujii@oss.nttdata.com>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-06-18T20:09:01Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add FLUSH_UNLOGGED option to CHECKPOINT command.
- 8d33fbacbac9 19 (unreleased) landed
Add MODE option to CHECKPOINT command.
- 2f698d7f4b7b 19 (unreleased) landed
Add option list to CHECKPOINT command.
- a4f126516e68 19 (unreleased) landed
Rename CHECKPOINT_FLUSH_ALL to CHECKPOINT_FLUSH_UNLOGGED.
- cd8324cc89a9 19 (unreleased) landed
Rename CHECKPOINT_IMMEDIATE to CHECKPOINT_FAST.
- bb938e2c3c7a 19 (unreleased) landed

Re: Nathan Bossart
> I broke this up into several small patches.  Notable changes are as
> follows:
> 
> * Adjusted to the tab completion code to work more like the VACUUM utility
>   options.
> 
> * Introduced a new ExecCheckpoint() function in checkpointer.c and moved
>   the privilege check and options parsing there.

Ack. I was pondering if the code was growing too big there, but didn't
want to change too many things at once.

> * Removed the notes in the docs about when to use the CHECKPOINT command.
>   I'm not opposed to adding something like that (in fact, I think it's a
>   good idea), but IMHO we should bikeshed on that separately, maybe even in
>   a new thread.

I would have thought this already happened here. 

> Thoughts?

Fine with me, thanks!

Christoph