Re: Setting pd_lower in GIN metapage
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Masahiko Sawada <sawada.mshk@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-10T16:26:33Z
Lists: pgsql-hackers
Amit Kapila <amit.kapila16@gmail.com> writes: > On Sun, Sep 10, 2017 at 11:52 AM, Michael Paquier > <michael.paquier@gmail.com> wrote: >> Coordinating efforts here would be nice. If you, Amit K, are taking >> care of a patch for btree and hash > I think here we should first agree on what we want to do. Based on > Tom's comment, I was thinking of changing comments in btree/hash part > and additionally for hash indexes, I can see if we can pass > REGBUF_STANDARD for all usages of metapage. I am not sure if we want > similar exercise for btree as well. FWIW, now that we've noticed the discrepancy, I'm for using REGBUF_STANDARD or equivalent for all metapage calls. Even if it saves no space, inconsistency is bad because it's confusing. And Michael is correct to point out that we can exploit this to improve WAL consistency checking. regards, tom lane
Commits
-
Flag index metapages as standard-format in xlog.c calls.
- 4c11d2c559e7 11.0 landed
-
Set the metapage's pd_lower correctly in brin, gin, and spgist indexes.
- 81e334ce4e6d 11.0 landed