| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Evgeny Morozov <postgresql3(at)realityexists(dot)net> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Alban Hertroys <haramrae(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-04 23:27:38 |
| Message-ID: | CA+hUKGK-=ELQ3ktiPGb3M43eKqV=yr6pPhRy0yR_hU0ittzCjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, May 5, 2023 at 11:15 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Now *that* is a piece of
> logic that changed in PostgreSQL 15. It changed from sector-based
> atomicity assumptions to a directory entry swizzling trick, in commit
> d8cd0c6c95c0120168df93aae095df4e0682a08a. Hmm.
I spoke too soon, that only changed in 16. But still, it means there
are two files that could be corrupted here, pg_filenode.map which
might somehow be pointing to the wrong file, and the relation (index)
main fork file.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-05-05 00:02:10 | Re: "PANIC: could not open critical system index 2662" - twice |
| Previous Message | Thomas Munro | 2023-05-04 23:15:18 | Re: "PANIC: could not open critical system index 2662" - twice |