From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: single user mode -P option is ignored |
Date: | 2018-12-19 18:06:37 |
Message-ID: | CAFj8pRCBwf2TOfbifeVEt2mHb54Whxc1G1E19A1u7E8DUTS=9g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
st 19. 12. 2018 v 19:01 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > st 19. 12. 2018 v 17:59 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> >> So either this is something we fixed since 9.5.5, or your summary
> >> of the problem is missing many critical details.
>
> > I got different error message "could not open critical system index". I
> > checked files, and related files was there.
>
> Hmm ... looking at the relcache code, it appears that could only happen
> if the pg_class entry for that index couldn't be found. Which probably
> means you've suffered catastrophic damage to pg_class --- there's no
> good reason to assume that only that one row has been clobbered.
> Reindexing isn't going to get you out of that :-(
>
I found this index in pg_class file . But that is all what I can say - I
don't know if this table is readable or not.
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-12-19 18:07:31 | Re: [HACKERS] Macros bundling RELKIND_* conditions |
Previous Message | Massimo Fidanza | 2018-12-19 18:02:07 | Re: GraalVM |