Re: Why is a newly created index contains the invalidLSN?

Поиск
Список
Период
Сортировка
От Yury Zhuravlev
Тема Re: Why is a newly created index contains the invalidLSN?
Дата
Msg-id e295d94b-17ed-4a71-82db-735ca4c928de@postgrespro.ru
обсуждение исходный текст
Ответ на Re: Why is a newly created index contains the invalid LSN?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Jim Nasby wrote:
> Yeah, especially since you mentioned this being for backups. I
> suspect you *want* those WAL records marked with 0, because that
> tells you that you can't rely on WAL when you back that data up.

Thanks, you right if you doing incremental backup you try compare every
page LSN with last backup LSN. For my page tracking system (ptrack) it is
secondary cheks but for classic pg_arman algorithm it is main approach.
If Invalid LSN will be realy sign of broken page header it help for
third-party applications.


--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



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

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: [PATCH] Transaction traceability - txid_status(bigint)
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: asynchronous and vectorized execution