|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Michael Paquier <michael(dot)paquier(at)gmail(dot)com>|
|Cc:||Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Setting pd_lower in GIN metapage|
|Views:||Raw Message | Whole Thread | Download mbox|
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Fri, Nov 3, 2017 at 1:10 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> On Fri, Nov 3, 2017 at 2:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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  for the same in this thread and
>> those are reviewed  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,
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
|Next Message||Andres Freund||2017-11-03 20:33:45||Re: [HACKERS] pgsql: Fix freezing of a dead HOT-updated tuple|
|Previous Message||Peter Geoghegan||2017-11-03 20:21:23||Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple|