Re: CHECKPOINT unlogged data

From: Christoph Berg <myon(at)debian(dot)org>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: CHECKPOINT unlogged data
Date: 2025-06-11 15:53:15
Message-ID: [email protected]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v4-0001-Rename-checkpoint-options-immediate-and-flush-all.patch text/x-diff 17.7 KB
v4-0002-Add-mode-and-flush_unlogged-options-to-CHECKPOINT.patch text/x-diff 10.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-06-11 16:07:59 Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Previous Message Peter Eisentraut 2025-06-11 15:22:53 Re: Proper object locking for GRANT/REVOKE