Re: Why is a newly created index contains the invalid LSN?

From: Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is a newly created index contains the invalid LSN?
Date: 2016-08-29 08:03:11
Message-ID: e295d94b-17ed-4a71-82db-735ca4c928de@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2016-08-29 08:08:36 Re: asynchronous and vectorized execution
Previous Message Craig Ringer 2016-08-29 07:53:34 Re: [PATCH] Transaction traceability - txid_status(bigint)