Re: [HACKERS] per-sesson errors after interrupting CLUSTER pg_attribute (not attrdef)

On Tue, Mar 20, 2018 at 01:03:57PM -0500, Justin Pryzby wrote:
> On Tue, Oct 24, 2017 at 04:56:27PM -0700, Michael Paquier wrote:
> > 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 (?)
>
> Now I know, this is still an issue under PG10.2:
>
> [pryzbyj(at)united-telsasoft ~]$ psql ts
> psql (10.2)
> ts=# CLUSTER VERBOSE pg_attribute USING pg_attribute_relid_attnum_index ;
> INFO: clustering "pg_catalog.pg_attribute" using sequential scan and sort
> INFO: "pg_attribute": found 18102 removable, 2488511 nonremovable row versions in 80769 pages
> DETAIL: 0 dead row versions cannot be removed yet.
> CPU: user: 10.00 s, system: 1.59 s, elapsed: 27.60 s.
> ^CCancel request sent
> ERROR: canceling statement due to user request
> ts=# CLUSTER VERBOSE pg_attribute USING pg_attribute_relid_attnum_index ;
> ERROR: could not open file "base/16400/948150297": No such file or directory

> I don't know much but..is this related to pg_filenode.map?

I gather this is the "prefer that it not happen" case here:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/utils/cache/relmapper.c;hb=HEAD#l449

So I think this is a known, accepted/expected behavior and no issue.

Justin