From: | CS DBA <cs_dba(at)consistentstate(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: checkpoint write errors ( getting worse ) |
Date: | 2016-10-23 03:46:41 |
Message-ID: | 5ef6cd91-59ed-d01f-0ca5-21a02b77a6aa@consistentstate.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
also, any thoughts on what could be causing these issues?
On 10/22/2016 05:59 PM, Tom Lane wrote:
> CS DBA <cs_dba(at)consistentstate(dot)com> writes:
>> So I ran REINDEX on all the db's and the errors went away for a bit. Now
>> I'm seeing this:
>> Log entries like this:FATAL: could not read block 0 of relation
>> base/1311892067/2687: read only 0 of 8192 bytes
> You have a problem there, because:
>
> regression=# select 2687::regclass;
> regclass
> ----------------------
> pg_opclass_oid_index
> (1 row)
>
> which is a pretty critical index.
>
> You might be able to fix this by starting a single-user backend with -P
> (--ignore-system-indexes) and using it to REINDEX that index.
>
> On the whole, though, it's starting to sound like that system has
> got major problems. You'd be well advised to focus all your efforts
> on getting a valid dump, not bringing it back into production.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2016-10-23 15:06:57 | Re: Exclude pg_largeobject form pg_dump |
Previous Message | CS DBA | 2016-10-23 03:45:53 | Re: checkpoint write errors ( getting worse ) |