On 4/05/2023 6:42 pm, Laurenz Albe wrote: > On Thu, 2023-05-04 at 15:49 +0000, Evgeny Morozov wrote: >> Well, the problem happened again! Kind of... This time PG has not >> crashed with the PANIC error in the subject, but pg_dumping certain DBs >> again fails with >> >> >> pg_dump: error: connection to server on socket >> "/var/run/postgresql/.s.PGSQL.5434" failed: FATAL: index >> "pg_class_oid_index" contains unexpected zero page at block 0 > If you dumped and restored the database after the last time the error > happened, there must be a systemic problem. I dumped and restored the "real" databases I cared about. The tests databases on which error now happens are new (created 2 days ago). > Perhaps you have bad hardware, or a problem with a storage driver, > file system or some other low-level software component. > It might of course be a PostgreSQL bug too, but it is hard to say > without a way to reproduce... I'm now thinking of setting up a dedicated AWS EC2 instance just for these little DBs that get created by our automated tests. If the problem happens there as well then that would strongly point towards a bug in PostgreSQL, wouldn't it? (And if nothing else, at least it won't affect the more important DBs!) Meanwhile, what do I do with the existing server, though? Just try to drop the problematic DBs again manually?
