Re: Why is a newly created index contains the invalidLSN? - Mailing list pgsql-hackers

From Yury Zhuravlev
Subject Re: Why is a newly created index contains the invalidLSN?
Date
Msg-id e295d94b-17ed-4a71-82db-735ca4c928de@postgrespro.ru
Whole thread Raw
In response to Re: Why is a newly created index contains the invalid LSN?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List 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 by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous and vectorized execution