From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Can't find a relation in pg_class |
Date: | 2018-11-15 19:57:38 |
Message-ID: | 244637b0-a121-d1f0-74b1-24c0facca308@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 11/15/2018 12:56 PM, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-11-15 20:02:08 | Re: Can't find a relation in pg_class |
Previous Message | Mariel Cherkassky | 2018-11-15 19:29:49 | Re: checkpoint occurs very often when vacuum full running |