| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Boblitz John <john(dot)boblitz(at)bertschi(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unable to Connect to DB Instance |
| Date: | 2018-07-04 15:49:57 |
| Message-ID: | 66417.1530719397@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
Boblitz John <john(dot)boblitz(at)bertschi(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-07-04 15:56:20 | Re: Unable to Connect to DB Instance |
| Previous Message | matshyeq | 2018-07-04 12:06:06 | Re: pgAdmin 4 v3.1 on MacOS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-07-04 15:56:20 | Re: Unable to Connect to DB Instance |
| Previous Message | hmidi slim | 2018-07-04 15:32:36 | Re: Return select statement with sql case statement |