Re: Few comments on commit 857f9c36 (skip full index scans ) - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Few comments on commit 857f9c36 (skip full index scans )
Date
Msg-id CAA4eK1+hU6u2PQz_vTyDq9iuaQvG1hoq6VYR71PG_KZ7PeEWMQ@mail.gmail.com
Whole thread Raw
In response to Re: Few comments on commit 857f9c36 (skip full index scans )  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Few comments on commit 857f9c36 (skip full index scans )  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
On Wed, May 30, 2018 at 9:09 PM, Teodor Sigaev <teodor@sigaev.ru> wrote:
>> The metapage upgrade should be performed under critical section.
>
>
> Agree. But after close look I found that btm_version change isn't wal-logged
> (near line 2251 in _bt_newroot). So btm_version is not propagated to
> replica/backup/etc.
>

I think it will always be set to BTREE_VERSION (See _bt_restore_meta).
I see that other places like _bt_insertonpg,
_bt_update_meta_cleanup_info, etc. that log meta page contents don't
log version number, so if we want to log it, all such places also need
to be modified, but I don't see the need for same.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Proposal: Partitioning Advisor for PostgreSQL
Next
From: Teodor Sigaev
Date:
Subject: Re: POC: GROUP BY optimization