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: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Tom Lane <tgl@sss.pgh.pa.us>, Masahiko Sawada <sawada.mshk@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-19T04:03:40Z
Lists: pgsql-hackers
On Tue, Sep 19, 2017 at 12:57 PM, Michael Paquier <michael.paquier@gmail.com> wrote: > I'd think about adjusting the comments the proper way for each AM so > as one can read those comments and catch any limitation immediately. > The fact this has not been pointed out on this thread before any > checks and the many mails exchanged on the matter on this thread make > me think that the current code does not outline the current code > properties appropriately. Another thing that we could consider as well is adding an assertion in XLogRegisterBuffer & friends so as the combination of REGBUF_STANDARD and REGBUF_NO_IMAGE is forbidden. That's bugging me as well. -- 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