pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Subject: FATAL: cache lookup failed for relation 1247
2+ messages / 2 participants
[nested] [flat]

* Subject: FATAL: cache lookup failed for relation 1247
@ 2023-10-11 06:05 Israr Khan <israr@amnex.com>
  2023-10-11 14:24 ` Re: Subject: FATAL: cache lookup failed for relation 1247 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Israr Khan @ 2023-10-11 06:05 UTC (permalink / raw)
  To: pgsql-general

Hey PgSQL ,

I am facing the postgresql database access issue after doing vacuum on a
table.
Please help and suggest as soon as possible.

Error : FATAL: cache lookup failed for relation 1247


Thank you
Israr

-- 
Disclaimer : This message (including any attachments) is sent on behalf of 
Amnex Infotechnologies Private Limited and contains confidential 
information intended for a specific individual and purpose, and is 
protected by law. If you are not the intended recipient, you should delete 
this message and are hereby notified that any disclosure, copying, or 
distribution of this message, or the taking of any action based on it, is 
strictly prohibited.

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Subject: FATAL: cache lookup failed for relation 1247
  2023-10-11 06:05 Subject: FATAL: cache lookup failed for relation 1247 Israr Khan <israr@amnex.com>
@ 2023-10-11 14:24 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2023-10-11 14:24 UTC (permalink / raw)
  To: Israr Khan <israr@amnex.com>; +Cc: pgsql-general

Israr Khan <israr@amnex.com> writes:
> I am facing the postgresql database access issue after doing vacuum on a
> table.

There has to have been more to it than that.

> Error : FATAL: cache lookup failed for relation 1247

1247 is pg_type, so this looks like rather nasty catalog corruption.
If you're really lucky, this might just be a messed-up index for
pg_class, but I'm afraid this might be something that calls for
professional data recovery help (if the data in that database is
valuable enough to you to justify that).

In any case, your first move should be to stop the postmaster and
make a physical backup (e.g. with tar) of the data directory.
Then at least you can get back to where you are if recovery
attempts make things worse.

After that, see if you can connect to that DB with system indexes
disabled, and if so try to issue REINDEX TABLE pg_class.

There's some other helpful info at

https://wiki.postgresql.org/wiki/Corruption

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2023-10-11 14:24 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-10-11 06:05 Subject: FATAL: cache lookup failed for relation 1247 Israr Khan <israr@amnex.com>
2023-10-11 14:24 ` Tom Lane <tgl@sss.pgh.pa.us>

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