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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "Todd A(dot) Cook" <ToddA(dot)Cook(at)synopsys(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
Date: 2018-08-14 21:25:33
Message-ID: CAH2-WzmFPQe2QYKG_MhQtvZGpw_4w=qAwap=aiuF+GinYDbOYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 14, 2018 at 2:07 PM, Todd A. Cook <ToddA(dot)Cook(at)synopsys(dot)com> wrote:
> Sorry, I just noticed this. Mantid is my animal, so I can set "min_parallel_table_scan_size = 0"
> on it if that would be helpful. (Please reply directly if so; I'm not able to keep up with pgsql-hackers
> right now.)

We've already been able to rule that out as a factor here. Thanks all
the same, though.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-08-14 21:26:30 Re: logical decoding / rewrite map vs. maxAllocatedDescs
Previous Message Mark Dilger 2018-08-14 21:14:54 Re: Facility for detecting insecure object naming