On 11/15/2018 12:56 PM, Tom Lane wrote:
Ron <ronljohnsonjr@xxxxxxxxx> 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.
