Re: Why are we PageInit'ing buffers in RelationAddExtraBlocks()?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Why are we PageInit'ing buffers in RelationAddExtraBlocks()?
Date: 2019-01-29 00:40:36
Message-ID: 20190129004036.c2cf3fxoescf2rvf@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2019-01-28 15:49:33 -0800, Andres Freund wrote:
> On 2019-01-28 18:08:59 -0500, Tom Lane wrote:
> > Andres Freund <andres(at)anarazel(dot)de> writes:
> > > I'm inclined to put back the
> > > LockBuffer(buf, BUFFER_LOCK_UNLOCK);
> > > LockRelationForExtension(onerel, ExclusiveLock);
> > > UnlockRelationForExtension(onerel, ExclusiveLock);
> > > LockBufferForCleanup(buf);
> > > if (PageIsNew(page))
> > > dance regardless, just to get the buildfarm to green?
> >
> > The buildfarm's got half a dozen reports now of a failure of this ilk,
> > so you'd better do something.
>
> Yea, I was working on a patch. Was trying to come up with an explanation
> of how this can be realistically hit on the BF, but failed. I've pushed
> something now, let's see whether that fixes it.

It has not. Given that I don't understand what's happening here I'm
going to revert both commits unless I figure it out in the next ~30min.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-01-29 00:51:22 Re: Header checking failures on LLVM-less machines
Previous Message Jamison, Kirk 2019-01-29 00:35:30 RE: pg_upgrade: Pass -j down to vacuumdb