pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Can't find a relation in pg_class
Date: Thu, 15 Nov 2018 14:09:55 -0600
Message-ID: <a9b3038e-af0d-2946-23e8-aff949f4c95a@gmail.com> (raw)
In-Reply-To: <20181115200208.lo3idqo3vvbb4vut@alvherre.pgsql>
References: <20181115200208.lo3idqo3vvbb4vut@alvherre.pgsql>

On 11/15/2018 02:02 PM, Alvaro Herrera wrote:
> On 2018-Nov-15, Ron wrote:
>
>> On 11/15/2018 12:56 PM, Tom Lane wrote:
>>> Ron <ronljohnsonjr@gmail.com> writes:
>>>> 10.143.169.100(38184) TAP TAPb 14310 PARSE waiting [unknown] 00000
>>>>           LOG:  process 14310 still waiting for AccessShareLock
>>>>           on relation *767445914* of database *767442254* after 1000.389 ms at
>>>> character 39
>>>> We found this in the log file, so went looking for what relation 767445914
>>>> is, but don't see it in the pg_class table.  Am I doing something wrong?
>>> This message would be citing relation OID not relfilenode, I believe.
>> In what table?
> select ... from pg_class where oid = 767445914

That's what I thought.  But select oid, relfilenode from pg_class shows that 
c.oid always has the same value as c.relfilenode.

-- 
Angular momentum makes the world go 'round.




view thread (6+ messages)  latest in thread

Message-ID: <a9b3038e-af0d-2946-23e8-aff949f4c95a@gmail.com>
Permalink:  ../a9b3038e-af0d-2946-23e8-aff949f4c95a@gmail.com/
Also on:    postgresql.org/message-id/a9b3038e-af0d-2946-23e8-aff949f4c95a@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Can't find a relation in pg_class
  In-Reply-To: <a9b3038e-af0d-2946-23e8-aff949f4c95a@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox