Re: Setting pd_lower in GIN metapage
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Amit Kapila <amit.kapila16@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-11-03T20:33:44Z
Lists: pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes: > On Fri, Nov 3, 2017 at 1:10 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> On Fri, Nov 3, 2017 at 2:54 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> I've marked the CF entry closed. However, I'm not sure if we're quite >>> done with this thread. Weren't we going to adjust nbtree and hash to >>> be more aggressive about labeling their metapages as REGBUF_STANDARD? >> I have already posted the patches [1] for the same in this thread and >> those are reviewed [2][3] as well. I have adjusted the comments as per >> latest commit. Please find updated patches attached. > Confirmed. Setting those makes sense even if REGBUF_WILL_INIT is set, > at least for page masking. Thanks, I'd forgotten those patches were already posted. Looks good, so pushed. Looking around, I noted that contrib/bloom also had the disease of not telling log_newpage it was writing a standard-format metapage, so I fixed that too. 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