Re: 10.5 but not 10.4: backend startup during reindex system: could not read block 0 in file "base/16400/..": read only 0 of 8192 bytes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 10.5 but not 10.4: backend startup during reindex system: could not read block 0 in file "base/16400/..": read only 0 of 8192 bytes
Date
Msg-id 18087.1535556951@sss.pgh.pa.us
Whole thread Raw
In response to 10.5 but not 10.4: backend startup during reindex system: could notread block 0 in file "base/16400/..": read only 0 of 8192 bytes  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: 10.5 but not 10.4: backend startup during reindex system: couldnot read block 0 in file "base/16400/..": read only 0 of 8192 bytes
List pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes:
> I've seen this message now a handful of times recently.  It seems to happen
> overnight, during a maintenance job which reindex things, including system
> catalog indices.
> It's easy to reproduce error under 10.5, but not under 10.3 nor 10.4.
> while :; do for a in pg_class_oid_index pg_class_relname_nsp_index pg_class_tblspc_relfilenode_index; do psql ts -qc
"REINDEXINDEX $a"; done; done& 

This looks suspiciously like the issue under discussion in

https://www.postgresql.org/message-id/12259.1532117714%40sss.pgh.pa.us

As far as we can tell, that bug is a dozen years old, so it's not clear
why you find that you can reproduce it only in 10.5.  But there might be
some subtle timing change accounting for that.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is child process of postmaster able to access all the databases?
Next
From: Erik Rijkers
Date:
Subject: rare crash - FailedAssertion snapbuild.c Line: 580