Re: CHECKPOINT unlogged data

Christoph Berg <myon@debian.org>

From: Christoph Berg <myon@debian.org>

To: Nathan Bossart <nathandbossart@gmail.com>

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

Date: 2025-06-11T15:53:15Z

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

Attachments

v4-0001-Rename-checkpoint-options-immediate-and-flush-all.patch (text/x-diff)

Re: Nathan Bossart
> IMO we should try to make the terminology consistent everywhere.  I'd
> suggest putting the renaming stuff in separate prerequisite patches for
> your new CHECKPOINT option.

Ack, done in v4.

I haven't implemented a WAIT option yet since I didn't want to decide
that without more votes in either direction.

Christoph