Re: Corruption during WAL replay
От | Robert Haas |
---|---|
Тема | Re: Corruption during WAL replay |
Дата | |
Msg-id | CA+TgmoZA=e9Cj0PuLPF7CpgCdJLqTT__5+HiwnopSpBwF--+2g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Corruption during WAL replay (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Corruption during WAL replay
|
Список | pgsql-hackers |
On Fri, Sep 24, 2021 at 3:42 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > I like this patch. > > I think the basic idea is about right, but I'm not happy with the > three-way delayChkpt business; that seems too cute by three-quarters. > I think two independent boolean flags, one saying "I'm preventing > checkpoint start" and one saying "I'm preventing checkpoint completion", > would be much less confusing and also more future-proof. Who's to say > that we won't ever need both states to be set in the same process? Nobody, but the version of the patch that I was looking at uses a separate bit for each one: +/* symbols for PGPROC.delayChkpt */ +#define DELAY_CHKPT_START (1<<0) +#define DELAY_CHKPT_COMPLETE (1<<1) One could instead use separate Booleans, but there doesn't seem to be anything three-way about this? -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: