Re: CHECKPOINT unlogged data
От | Andres Freund |
---|---|
Тема | Re: CHECKPOINT unlogged data |
Дата | |
Msg-id | 7x6gsmev36zzh6lfzydkddbhpnxqgu2k2l2ci2k6foxhrstvj2@bn55g54wjrl4 обсуждение исходный текст |
Ответ на | Re: CHECKPOINT unlogged data (Christoph Berg <myon@debian.org>) |
Ответы |
Re: CHECKPOINT unlogged data
|
Список | pgsql-hackers |
On 2025-05-30 19:23:04 +0200, Christoph Berg wrote: > Re: Nathan Bossart > > 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 > > Thanks for the pointer, I did not go that far back when looking for > older threads. > > When writing the patch, I was also thinking about naming the option > "fast" or "spread" but ultimately went with "immediate" because that's > what the log message is using: > > =# checkpoint; > 2025-05-30 18:23:17.433 CEST [579834] LOG: Checkpoint beginnt: immediate force wait > > SQL command "(options)" tend to be booleans, hence "immediate {on|off}". > Introducing two separate keywords "fast" and "spread" seemed > confusing, and there is no precedent for "fast=on" in other tools or > the replication protocol. I'd add a 'mode' that can be set to an arbitrary string, which then can be validated in C code. That seems more future proof.
В списке pgsql-hackers по дате отправления: