Re: "PANIC: could not open critical system index 2662" - twice

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> 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.

Per the release notes I was just writing ...

<listitem>
<!--
Author: Michael Paquier <michael(at)paquier(dot)xyz>
Branch: master [8a8661828] 2023-02-22 10:14:52 +0900
Branch: REL_15_STABLE [fa5dd460c] 2023-02-22 10:14:56 +0900
-->
<para>
Fix potential corruption of the template (source) database after
<command>CREATE DATABASE</command> with the <literal>STRATEGY
WAL_LOG</literal> option (Nathan Bossart, Ryo Matsumura)
</para>

<para>
Improper buffer handling created a risk that any later modification
of the template's <structname>pg_class</structname> catalog would be
lost.
</para>
</listitem>

The comment about only pg_class being affected is my interpretation
of what the commit message said, but I might have misunderstood.

regards, tom lane