pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedBug in PostgreSQL
5+ messages / 5 participants
[nested] [flat]
* Bug in PostgreSQL
@ 2018-06-27 15:30 Rambabu V <ram.wissen@gmail.com>
0 siblings, 2 replies; 5+ messages in thread
From: Rambabu V @ 2018-06-27 15:30 UTC (permalink / raw)
To: pgsql-performance
Hi Team,
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Bug in PostgreSQL
@ 2018-06-27 15:50 Steve Crawford <scrawford@pinpointresearch.com>
parent: Rambabu V <ram.wissen@gmail.com>
1 sibling, 1 reply; 5+ messages in thread
From: Steve Crawford @ 2018-06-27 15:50 UTC (permalink / raw)
To: Rambabu V <ram.wissen@gmail.com>; +Cc: pgsql-performance
On Wed, Jun 27, 2018 at 8:31 AM Rambabu V <ram.wissen@gmail.com> wrote:
> Hi Team,
>
> 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.
>
Searching on that error messages yields a suggestion from Tom Lane to try
that select with enable_indexscan and enable_bitmapscan
turned off.
This question is probably better asked in the "General" mailing list. Also
please include the OS and PostgreSQL version as well as any other
observations that may shed light on the issue.
Cheers,
Steve
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Bug in PostgreSQL
@ 2018-06-27 15:53 Joseph Curtin <jbcurtincode@gmail.com>
parent: Steve Crawford <scrawford@pinpointresearch.com>
0 siblings, 0 replies; 5+ messages in thread
From: Joseph Curtin @ 2018-06-27 15:53 UTC (permalink / raw)
To: Steve Crawford <scrawford@pinpointresearch.com>; +Cc: Rambabu V <ram.wissen@gmail.com>; pgsql-performance
OID is a temp-var that is only consistent within a Query Execution.
https://www.postgresql.org/docs/current/static/datatype-oid.html
On Thu, Jun 28, 2018 at 12:50 AM, Steve Crawford <
scrawford@pinpointresearch.com> wrote:
>
>
> On Wed, Jun 27, 2018 at 8:31 AM Rambabu V <ram.wissen@gmail.com> wrote:
>
>> Hi Team,
>>
>> 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.
>>
>
> Searching on that error messages yields a suggestion from Tom Lane to try
> that select with enable_indexscan and enable_bitmapscan
> turned off.
>
> This question is probably better asked in the "General" mailing list. Also
> please include the OS and PostgreSQL version as well as any other
> observations that may shed light on the issue.
>
> Cheers,
> Steve
>
--
-Joseph Curtin
http://www.jbcurtin.com
<http://www.jbcurtin.com/>github <http://goo.gl/d5uPH;
@jbcurtin
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Bug in PostgreSQL
@ 2018-06-28 06:55 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Rambabu V <ram.wissen@gmail.com>
1 sibling, 1 reply; 5+ messages in thread
From: Laurenz Albe @ 2018-06-28 06:55 UTC (permalink / raw)
To: Rambabu V <ram.wissen@gmail.com>; pgsql-performance
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.
If possible, restore from a backup.
Did you experiences any crashes recently? Is your storage reliable?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Bug in PostgreSQL
@ 2018-06-28 16:13 Andres Freund <andres@anarazel.de>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 5+ messages in thread
From: Andres Freund @ 2018-06-28 16:13 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: Rambabu V <ram.wissen@gmail.com>; pgsql-performance
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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2018-06-28 16:13 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-06-27 15:30 Bug in PostgreSQL Rambabu V <ram.wissen@gmail.com>
2018-06-27 15:50 ` Steve Crawford <scrawford@pinpointresearch.com>
2018-06-27 15:53 ` Joseph Curtin <jbcurtincode@gmail.com>
2018-06-28 06:55 ` Laurenz Albe <laurenz.albe@cybertec.at>
2018-06-28 16:13 ` Andres Freund <andres@anarazel.de>
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