pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Evgeny Morozov <postgresql3@realityexists.net>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: Sat, 06 May 2023 21:21:30 -0400
Message-ID: <4029098.1683422490@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+hUKGJDfBEfqatSsV16XosCkr=3k2vb6X1mcbL_kdod_wHQwQ@mail.gmail.com>
References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com>
	<8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at>
	<010201877eb3c125-d9aff979-cad6-407b-8b4e-012487666088-000000@eu-west-1.amazonses.com>
	<A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com>
	<01020187e773e031-eecea370-714f-4858-82e5-ed1c9091eb6f-000000@eu-west-1.amazonses.com>
	<a64bb8dcbe5e0e0775c81db43e61a773f355df09.camel@cybertec.at>
	<01020187e7f5a96c-9bd4497c-abff-4c91-8a3f-e751a1f7d4b4-000000@eu-west-1.amazonses.com>
	<CA+hUKGJPuhFRN6dwZ=Y6SfMGYy8UHn3ueki-hafWeKA2t0zfEA@mail.gmail.com>
	<CA+hUKGLwDBnVHbef=p-BonSfiU1-XRoEg3ShECRZJFx2ti=TuQ@mail.gmail.com>
	<01020187eae42315-1cc83aed-2b4f-4c9e-ae36-ee82778f7154-000000@eu-west-1.amazonses.com>
	<CA+hUKGK7A42wpGvW3HouYAy+ud9c_8=5=jsaByR2-oxnbFkpZA@mail.gmail.com>
	<01020187f07f341f-d1593cf8-4fc7-4186-b70c-0c8862a2aa32-000000@eu-west-1.amazonses.com>
	<CA+hUKGJ-yWVQGJQiK5XHpD+97Qc533mNr1L=-sOQmCqDYoMB-w@mail.gmail.com>
	<0102018! 7f109fdd0-a5cfdb9a-6118-430f-b052-0d720f57620b-000000@eu-west-1.amazonses.com>
	<CA+hUKGJDfBEfqatSsV16XosCkr=3k2vb6X1mcbL_kdod_wHQwQ@mail.gmail.com>

Thomas Munro <thomas.munro@gmail.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@paquier.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





view thread (65+ messages)  latest in thread

Message-ID: <4029098.1683422490@sss.pgh.pa.us>
Permalink:  ../4029098.1683422490@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4029098.1683422490@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, postgresql3@realityexists.net
  Subject: Re: "PANIC: could not open critical system index 2662" - twice
  In-Reply-To: <4029098.1683422490@sss.pgh.pa.us>
  References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com> <A312EDE5-838F-4D81-BFA3-C269BAA3F68F@gmail.com> <01020187e773e031-eecea370-714f-4858-82e5-ed1c9091eb6f-000000@eu-west-1.amazonses.com> <a64bb8dcbe5e0e0775c81db43e61a773f355df09.camel@cybertec.at> <01020187e7f5a96c-9bd4497c-abff-4c91-8a3f-e751a1f7d4b4-000000@eu-west-1.amazonses.com> <CA+hUKGJPuhFRN6dwZ=Y6SfMGYy8UHn3ueki-hafWeKA2t0zfEA@mail.gmail.com> <CA+hUKGLwDBnVHbef=p-BonSfiU1-XRoEg3ShECRZJFx2ti=TuQ@mail.gmail.com> <01020187eae42315-1cc83aed-2b4f-4c9e-ae36-ee82778f7154-000000@eu-west-1.amazonses.com> <CA+hUKGK7A42wpGvW3HouYAy+ud9c_8=5=jsaByR2-oxnbFkpZA@mail.gmail.com> <01020187f07f341f-d1593cf8-4fc7-4186-b70c-0c8862a2aa32-000000@eu-west-1.amazonses.com> <CA+hUKGJ-yWVQGJQiK5XHpD+97Qc533mNr1L=-sOQmCqDYoMB-w@mail.gmail.com> <CA+hUKGJDfBEfqatSsV16XosCkr=3k2vb6X1mcbL_kdod_wHQwQ@mail.gmail.com> <4029098.1683422490@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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