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

From Jim Nasby
Subject Re: Why is a newly created index contains the invalid LSN?
Date
Msg-id 1e71b9df-918c-c336-5562-eee88a2856cf@BlueTreble.com
Whole thread Raw
In response to Re: Why is a newly created index contains the invalid LSN?  (Andres Freund <andres@anarazel.de>)
Responses Re: Why is a newly created index contains the invalidLSN?  (Yury Zhuravlev <u.zhuravlev@postgrespro.ru>)
List pgsql-hackers
On 8/26/16 4:17 PM, Andres Freund wrote:
> On 2016-08-26 18:46:42 +0300, Yury Zhuravlev wrote:
>> Thanks all.
>> Now understand LSN strongly connected with WAL.
>> However how difficult put last system LSN instead 0?
>> It's not so important but will allow make use LSN more consistent.
>
> Maybe explain why you're interested in page lsns, that'd perhaps allow
> us to give more meaningful feedback.

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.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Kuntal Ghosh
Date:
Subject: Re: WAL consistency check facility