From: Andres Freund <andres@anarazel.de>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Rambabu V <ram.wissen@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Bug in PostgreSQL
Date: Thu, 28 Jun 2018 09:13:16 -0700
Message-ID: <20180628161316.jbzzo76kzcmczh2r@alap3.anarazel.de> (raw)
In-Reply-To: <1530168921.2415.13.camel@cybertec.at>
References: <CADtiZxpKon6FCaAuJ2v9sMgYmSMN3sq1GHXVUQ-v2UtW3JMVgQ@mail.gmail.com>
<1530168921.2415.13.camel@cybertec.at>
Hi,
On 2018-06-28 08:55:21 +0200, Laurenz Albe wrote:
> Rambabu V wrote:
> > While taking pgdump we are getting error message cache lookup failed for function 7418447.
> > While trying select * from pg_proc where oid=7418447 returns zero rows. Please help us on this.
>
> That means that some catalog data are corrupted.
It does *NOT* have mean that. You can get such reports e.g. because
there was concurrent DDL. Most things are protected against via locks,
but there's enough of a window between getting the list of objects and
locking to cause issues for tables. And for functions it's fairly easy
to get into trouble because there's a mismatch between the snapshot
pg_dump uses (a normal transactional snapshot) and the snapshot used to
deparse expressions etc (a fresh catalog snapshot that takes into
account concurrent commits).
Greetings,
Andres Freund
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-performance@postgresql.org
Cc: andres@anarazel.de, laurenz.albe@cybertec.at, ram.wissen@gmail.com
Subject: Re: Bug in PostgreSQL
In-Reply-To: <20180628161316.jbzzo76kzcmczh2r@alap3.anarazel.de>
* 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