Re: Corruption during WAL replay

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Corruption during WAL replay
Дата
Msg-id CA+TgmobXjkeptO-rNiOrq8zjUK2QusXKGgsRL-fqPCL0umc+3Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Corruption during WAL replay  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Corruption during WAL replay  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Corruption during WAL replay  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
On Fri, Mar 25, 2022 at 10:34 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I dunno.  Compatibility and speed concerns aside, that seems like an awful
> lot of bits to be expending on every page compared to the value.

I dunno either, but over on the TDE thread people seemed quite willing
to expend like 16-32 *bytes* for page verifiers and nonces and things.
For compatibility and speed reasons, I doubt we could ever get by with
doing that in every cluster, but I do have some hope of introducing
something like that someday at least as an optional feature. It's not
like a 16-bit checksum was state-of-the-art even when we introduced
it. We just did it because we had 2 bytes that we could repurpose
relatively painlessly, and not any larger number. And that's still the
case today, so at least in the short term we will have to choose some
other solution to this problem.

--
Robert Haas
EDB: http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Japin Li
Дата:
Сообщение: Re: pg_relation_size on partitioned table
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Add index scan progress to pg_stat_progress_vacuum