| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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-29 03:27:14 |
| Message-ID: | 20180829032714.6yu3bxdywcvyj2li@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-08-28 23:18:25 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Tom, I think this could use your eyes.
>
> I've had no luck reproducing it locally ... do you have a recipe
> for that?
It can reproduce reliably with the three scripts attached:
psql -c' drop table if exists t; create table t (a serial primary key, b int, c int);' && pgbench -n -c 4 -T300 -f /tmp/insert.sql
pgbench -n -c 4 -T300 -f /tmp/vacuum.sql
pgbench -n -c 4 -T300 -f /tmp/analyze.sql
Locally that triggers the problem within usually a few seconds.
Greetings,
Andres Freund
| Attachment | Content-Type | Size |
|---|---|---|
| insert.sql | application/x-sql | 34 bytes |
| vacuum.sql | application/x-sql | 21 bytes |
| analyze.sql | application/x-sql | 11 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-08-29 03:29:08 | Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes |
| Previous Message | Tom Lane | 2018-08-29 03:18:25 | Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes |