Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
Date
Msg-id 14220.1536176805@sss.pgh.pa.us
Whole thread Raw
In response to Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Andres Freund <andres@anarazel.de> writes:
>> One concern I have with your approach is that it isn't particularly
>> bullet-proof for cases where the rebuild is triggered by something that
>> doesn't hold a conflicting lock.

> Wouldn't that be a bug in the something-else?

So where are we on this?  Should I proceed with my patch, or are we
going to do further investigation?  Does anyone want to do an actual
patch review?

I think it's important to have some fix in place in time for the next
11beta release, so time grows short ...

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: On the need for a snapshot in exec_bind_message()
Next
From: Michael Paquier
Date:
Subject: Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.