From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rod Taylor <rbt@rbt.ca>
Cc: Thusitha Maheepala <thusitha@onsys.com.au>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Postgredb issue
Date: Sat, 09 May 2020 11:49:29 -0400
Message-ID: <5216.1589039369@sss.pgh.pa.us> (raw)
In-Reply-To: <CAHz80e54q_BuxxnK8z-9fhdJVz9dR+VQ6tU1CX0h=Ma2BD-sdw@mail.gmail.com>
References: <CABVa+CW3kTQG4=+34orDrJjyctRj+eeAhFGePc6Ka+7nOSxy-Q@mail.gmail.com>
<CAHz80e54q_BuxxnK8z-9fhdJVz9dR+VQ6tU1CX0h=Ma2BD-sdw@mail.gmail.com>
Rod Taylor <rbt@rbt.ca> writes:
> It appears all errors are related to the c_acctprocessorlog_pkey index? Run
> the below to ditch the current index and rebuild with data from the table
> files.
> REINDEX INDEX c_acctprocessorlog_pkey;
That appears to have been the original problem, but at the end of the
log we see that the database is refusing to start, which suggests some
other filesystem corruption has manifested. I'm suspecting some
combination of unreliable storage, ancient/buggy Postgres version etc.
It's troubling that the "last completed transaction" log messages suggest
that no checkpoint has completed since last July ... has the OP somehow
turned off checkpoints? Ordinarily the only thing that could prevent
checkpoint completion is I/O errors, but there's no trace of such in the
log. I wonder how much WAL has accumulated in the pg_wal/pg_xlog area.
It's possible that a professional data recovery service could help you
get something out of this mess. If the data is worth money to you,
see [1] for some places to try. Otherwise, chalk it up to experience
and start over.
regards, tom lane
[1] https://www.postgresql.org/support/professional_support/
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, rbt@rbt.ca, thusitha@onsys.com.au, pgsql-bugs@lists.postgresql.org
Subject: Re: Postgredb issue
In-Reply-To: <5216.1589039369@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