chance.
Regards,
John Boblitz
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Mittwoch, 4. Juli 2018 21:37
> To: Boblitz John
> Cc: pgsql-gene...@postgresql.org
> Subject: Re: Unable to Connect to DB Instance
>
> Boblitz John writes:
&g
On 07/04/2018 12:36 PM, Tom Lane wrote:
Boblitz John writes:
Thanks - I get "pg_db_role_setting" as a response.
Hm ... not its index? If the table itself is gone, it's surprising
that you can get through session startup.
I have already attempted to reindex system but get:
I had in mind j
Boblitz John writes:
> Thanks - I get "pg_db_role_setting" as a response.
Hm ... not its index? If the table itself is gone, it's surprising
that you can get through session startup.
> I have already attempted to reindex system but get:
I had in mind just reindexing the specific table you're h
sss.pgh.pa.us]
> Sent: Mittwoch, 4. Juli 2018 17:50
> To: Boblitz John
> Cc: pgsql-gene...@postgresql.org
> Subject: Re: Unable to Connect to DB Instance
>
> Boblitz John writes:
> > 2. Users reported messages similar to "could not open file
> "gl
On 07/04/2018 04:08 AM, Boblitz John wrote:
Good Morning,
Beginning yesterday morning, users have been unable to fully connect
to our DB Instance.
1.At the time of the initial report – I was connected to the DB via
pgAdmin and could perform queries without problem.
2.
Boblitz John 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
