Re: BUG #15000: Cache lookup failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Kellerer <thomas(at)kellerer(dot)eu>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15000: Cache lookup failure
Date: 2018-01-08 15:35:11
Message-ID: 30854.1515425711@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Kellerer <thomas(at)kellerer(dot)eu> writes:
> Tom Lane schrieb am 08.01.2018 um 16:12:
>> Hmph. Is it always the same OID in the message and the reported query?

> No, it's not always the same OID.

OK. The explanation then presumably is that something is dropping that
table concurrently with the pg_dump run. It remains unclear to me why
pg_dump is failing to protect itself against such a drop, but before we
can figure that out, we need to be able to reproduce the situation.
Can you identify anything that would be dropping tables concurrently
with this script?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Kellerer 2018-01-08 15:49:20 Re: BUG #15000: Cache lookup failure
Previous Message Thomas Kellerer 2018-01-08 15:27:24 Re: BUG #15000: Cache lookup failure