From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
Date: Thu, 09 Aug 2018 01:03:34 -0400
Message-ID: <1938.1533791014@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-WznAuzsQHAObT5+neO50=_PSJYhU_npp65MHaYjdKuM=ng@mail.gmail.com>
References: <12259.1532117714@sss.pgh.pa.us>
<20180720202450.zcakbvyqksschz5e@alap3.anarazel.de>
<20180725230736.nscpb5ad2tl64nez@alap3.anarazel.de>
<CAH2-WzmfC3WuVKCvBtS1agKs5kRu8uKnp_+VReYgD8D1XD0v5A@mail.gmail.com>
<27669.1533782451@sss.pgh.pa.us>
<CAH2-WznAuzsQHAObT5+neO50=_PSJYhU_npp65MHaYjdKuM=ng@mail.gmail.com>
Peter Geoghegan <pg@bowt.ie> writes:
> On Wed, Aug 8, 2018 at 7:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Oooh ... but pg_class wouldn't be big enough to get a parallel
>> index rebuild during that test, would it?
> Typically not, but I don't think that we can rule it out right away.
Hmmm ... maybe we should temporarily stick in an elog(LOG) showing whether
a parallel build happened or not, so that we can check the buildfarm logs
next time we see that failure?
> I don't know all that much about the buildfarm client code, and it's
> late.
It doesn't really stick in any undocumented configuration changes,
AFAIK. Possibly Andrew would have some more insight.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, andrew@dunslane.net, andres@anarazel.de, pgsql-hackers@lists.postgresql.org
Subject: Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
In-Reply-To: <1938.1533791014@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox