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 13:57:38 -0600
Message-ID: <244637b0-a121-d1f0-74b1-24c0facca308@gmail.com> (raw)
In-Reply-To: <17469.1542308167@sss.pgh.pa.us>
References: <b7852f9d-e530-2ae6-f77b-2c17f3eed414@gmail.com>
<17469.1542308167@sss.pgh.pa.us>
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?
> Another possibility is that you can't see the row because it's either
> uncommitted (new table) or committed dead (just-deleted table). But
> it's not real clear how there could be a lock conflict in such cases.
That's what puzzles us. (It's part of a huge transaction which drops old
bits of partitoned tables and then adds new bits. It worked flawlessly in
8.4 but not in 9.6.)
--
Angular momentum makes the world go 'round.
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: <244637b0-a121-d1f0-74b1-24c0facca308@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