Re: [HACKERS] per-sesson errors after interrupting CLUSTER pg_attrdef
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] per-sesson errors after interrupting CLUSTER pg_attrdef |
Дата | |
Msg-id | CAB7nPqSKp8C_Nn+HvS_EhWnDHBwiOrDUw4+kZNM0y2vtNpY=WQ@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] per-sesson errors after interrupting CLUSTER pg_attrdef (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: [HACKERS] per-sesson errors after interrupting CLUSTERpg_attribute (not attrdef)
|
Список | pgsql-hackers |
On Fri, Oct 20, 2017 at 9:01 AM, Justin Pryzby <pryzby@telsasoft.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: