Hello Tom, Thanks - I get "pg_db_role_setting" as a response.
I have already attempted to reindex system but get: NOTICE: table "pg_catalog.pg_class" was reindexed NOTICE: table "pg_catalog.pg_statistic" was reindexed NOTICE: table "pg_catalog.pg_type" was reindexed NOTICE: table "pg_catalog.pg_attribute" was reindexed NOTICE: table "pg_catalog.pg_authid" was reindexed ERROR: could not open file "base/11919/11680": No such file or directory John > -----Original Message----- > From: Tom Lane [mailto:t...@sss.pgh.pa.us] > Sent: Mittwoch, 4. Juli 2018 17:50 > To: Boblitz John <john.bobl...@bertschi.com> > Cc: pgsql-gene...@postgresql.org > Subject: Re: Unable to Connect to DB Instance > > Boblitz John <john.bobl...@bertschi.com> writes: > > 2. Users reported messages similar to "could not open file > "global/11801": No such file or directory" > > I'd try "select relname from pg_class where pg_relation_filenode(oid) = > 11801" to see if you can identify the problematic relation that way. > > If you're lucky, this is just loss of some system catalog index in which case > reindexing will fix it. The fact that you're able to get through connecting, > and the errors only show up with queries, is somewhat promising given that > the problem looks like it's related to pg_authid or pg_db_role_setting. > > regards, tom lane
