| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Can't find a relation in pg_class |
| Date: | 2018-11-15 18:56:07 |
| Message-ID: | 17469.1542308167@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-11-15 19:10:42 | Re: checkpoint occurs very often when vacuum full running |
| Previous Message | Mariel Cherkassky | 2018-11-15 18:53:14 | checkpoint occurs very often when vacuum full running |