Re: per-sesson errors after interrupting CLUSTER pg_attrdef

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: per-sesson errors after interrupting CLUSTER pg_attrdef
Date: 2017-10-24 23:56:27
Message-ID: CAB7nPqSKp8C_Nn+HvS_EhWnDHBwiOrDUw4+kZNM0y2vtNpY=WQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 20, 2017 at 9:01 AM, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> This was briefly scary but seems to have been limited to my psql session (no
> other errors logged). Issue with catcache (?)
>
> I realized that the backup job I'd kicked off was precluding the CLUSTER from
> running, but that CLUSTER was still holding lock and stalling everything else
> under the sun.
>
> ts=# \df qci_add*
> ERROR: could not read block 8 in file "base/16400/999225102": read only 0 of 8192 bytes
> ts=# \dt+ pg_att
>
> ts=# \dt+ pg_attrdef
> ERROR: could not read block 8 in file "base/16400/999225102": read only 0 of 8192 bytes

Perhaps that's too late, but to which relation is this relfilenode
actually referring to?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-10-25 00:37:18 Implementing pg_receivewal --no-sync
Previous Message Justin Pryzby 2017-10-24 22:28:40 Re: unique index violation after pg_upgrade to PG10