Re: Setting pd_lower in GIN metapage
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Masahiko Sawada <sawada.mshk@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-20T04:07:57Z
Lists: pgsql-hackers
On Wed, Sep 20, 2017 at 12:49 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Wed, Sep 20, 2017 at 4:25 AM, Michael Paquier > <michael.paquier@gmail.com> wrote: >> Also, _hash_init() would need some extra work to >> generate FPWs, but I don't think that it is necessary per its handling >> of a per-record meta data either. So REGBUF_STANDARD could be just >> removed from there, and there is actually no need to patch >> src/backend/access/hash at all. >> > > I think there is no need to remove it. As per discussion above, we > want to keep REGBUF_STANDARD for all metapage initializations for the > matter of consistency and that will be useful for > wal_consistency_checking in which case we anyway need full page image. Arf, yes. You are indeed right. I misread that you still need that anyway in XLogRecordAssemble. -- Michael
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