pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: "PANIC: could not open critical system index 2662" - twice
Date: Thu, 4 May 2023 13:16:37 -0500
Message-ID: <da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com> (raw)
In-Reply-To: <01020187e7f5a96c-9bd4497c-abff-4c91-8a3f-e751a1f7d4b4-000000@eu-west-1.amazonses.com>
References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com>
	<4f4ab16320d7b3a4e9950eaabde752dce204dc77.camel@cybertec.at>
	<010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com>
	<ZDX87IYoz0GU9CKy@paquier.xyz>
	<010201877966fc0d-e09f5a0b-e846-417b-b30a-b8d57ac61fa3-000000@eu-west-1.amazonses.com>
	<c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.camel@cybertec.at>
	<010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-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>

On 5/4/23 13:10, Evgeny Morozov wrote:
[snip]
> I'm now thinking of setting up a dedicated AWS EC2 instance just for
> these little DBs that get created by our automated tests. If the problem
> happens there as well then that would strongly point towards a bug in
> PostgreSQL, wouldn't it?

Many other people besides you would have noticed regular corruption of 
system catalogs.

> Meanwhile, what do I do with the existing server, though? Just try to
> drop the problematic DBs again manually?

*"Fix the hardware"* is what you do.

-- 
Born in Arizona, moved to Babylonia.

view thread (65+ messages)  latest in thread

Message-ID: <da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com>
Permalink:  ../da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com/
Also on:    postgresql.org/message-id/da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com

 · 

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: ronljohnsonjr@gmail.com
  Subject: Re: "PANIC: could not open critical system index 2662" - twice
  In-Reply-To: <da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com>
  References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com> <4f4ab16320d7b3a4e9950eaabde752dce204dc77.camel@cybertec.at> <010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com> <ZDX87IYoz0GU9CKy@paquier.xyz> <010201877966fc0d-e09f5a0b-e846-417b-b30a-b8d57ac61fa3-000000@eu-west-1.amazonses.com> <c6a6f6c7a3e9a707ac7b28cefeca67d045ecc63a.camel@cybertec.at> <010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-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> <da96d066-6ad3-0e10-110d-41bbf95231e6@gmail.com>

* 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