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

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is a newly created index contains the invalid LSN?
Date: 2016-08-26 21:13:07
Message-ID: CACjxUsMod4DiNTgt_AWwzU0p_vUZM6dEbwmK_UTCC5U_fEAcUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 26, 2016 at 10:46 AM, Yury Zhuravlev
<u(dot)zhuravlev(at)postgrespro(dot)ru> wrote:

> 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.

There might be performance implications when flushing the index
buffers, due to the need to check each one against the WAL flush
point, where we now skip that check.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-08-26 21:15:41 Re: Renaming of pg_xlog and pg_clog
Previous Message Peter Eisentraut 2016-08-26 21:11:00 Re: Renaming of pg_xlog and pg_clog