| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Evgeny Morozov <postgresql3(at)realityexists(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "PANIC: could not open critical system index 2662" - twice |
| Date: | 2023-05-08 09:53:49 |
| Message-ID: | 20230508095349.ie2sr3eldmtvuqcw@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2023-May-07, Thomas Munro wrote:
> Did you previously run this same workload on versions < 15 and never
> see any problem? 15 gained a new feature CREATE DATABASE ...
> STRATEGY=WAL_LOG, which is also the default. I wonder if there is a
> bug somewhere near that, though I have no specific idea. If you
> explicitly added STRATEGY=FILE_COPY to your CREATE DATABASE commands,
> you'll get the traditional behaviour.
Maybe it would be sensible to make STRATEGY_FILE=FILE_COPY the default
again, for branch 15, before today's release.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Doing what he did amounts to sticking his fingers under the hood of the
implementation; if he gets his fingers burnt, it's his problem." (Tom Lane)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Age Apache | 2023-05-08 10:24:06 | Additive backup and restore? |
| Previous Message | Evgeny Morozov | 2023-05-08 09:19:23 | Re: "PANIC: could not open critical system index 2662" - twice |