Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pwCF0-0004qI-46 for pgsql-general@arkaria.postgresql.org; Tue, 09 May 2023 01:34:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pwCDz-0003Po-TG for pgsql-general@arkaria.postgresql.org; Tue, 09 May 2023 01:33:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pwCDz-0003Pf-Hg for pgsql-general@lists.postgresql.org; Tue, 09 May 2023 01:33:07 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pwCDt-001Tz8-VN for pgsql-general@postgresql.org; Tue, 09 May 2023 01:33:06 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 631E3320046F; Mon, 8 May 2023 21:32:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 08 May 2023 21:32:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1683595978; x=1683682378; bh=J+ LwKZKocRKB+d3A5Au5zgCZ+4+EtmEugw7eBmmO2Ck=; b=qvlqAEWd/RPvTRFBHV IhcBa6D7PMqYAkfNjqeUYUCXJ10stFhW7rbqGUlXSV4taFu2VKkiLcY6F2ckqvFF EqVhrDYmR42KelIFgGKiM0TJCOam3+6WG50DjhhYCR7JT9coLw5U4gEC51MvOxQl Zfg+XKaJ9EOkotHUmFtkB/Hkcf2L88cCJrS0NAwn2UFve0wbUa2om8Hk7EGjvoFm HvlprNUmzMZCmw+khV7oXshZqzYtdeA7TSeHzBwgCxUT1IdamdaO2qfU5cAq44qs VswowhHUBUQUOjI+MGtt/bRlhbfq7IrTmCPfW1W+JxoVRy/AxzjLPiI4FR5p4UBk PXyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1683595978; x=1683682378; bh=J+LwKZKocRKB+ d3A5Au5zgCZ+4+EtmEugw7eBmmO2Ck=; b=MlPFmQ6lg5ipGaHF8iCT+BEnS6r9V psznUmAb4GvNJ8apxuB31ubj7blQls2GLdSTxIza/wOhiiS0PQl7ZOa4E704YvID mwyhWfi7rW0vyeltoUozeqB8b/tiu2t7AvBpra7yLMScdzjSRdRaQqThHDZrrwCL XNtGHaWdvb6Kh3ikzESos02Py8Iul04FNSCKfY5dT0Dg0ToovOwXVIrrEdcx1Okp OpLgO28uCNUHzeIuU5YxoWTRuMiBRGzMIMEdNSikEaz35mM+PJygZYQf+hpJqKXI +jeyFS88ny3ubx8B1wIdZzKkYvlYk8xofz5lY8fJjgCNgvFKZxMdFE9yA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefledggeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesmhdtreertddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhepfeduteegkeffheevveeluefhfeeileelvdevheeukeeitdeuvdffhefg hfeludeinecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghr rgiivghlrdguvg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 May 2023 21:32:57 -0400 (EDT) Date: Mon, 8 May 2023 18:32:55 -0700 From: Andres Freund To: Evgeny Morozov Cc: Thomas Munro , Tom Lane , PostgreSQL General Subject: Re: "PANIC: could not open critical system index 2662" - twice Message-ID: <20230509013255.fjrlpitnj3ltur76@awork3.anarazel.de> References: <01020187f07f341f-d1593cf8-4fc7-4186-b70c-0c8862a2aa32-000000@eu-west-1.amazonses.com> <4029098.1683422490@sss.pgh.pa.us> <01020187f6fa8f05-d1bd9975-48ec-4d8d-9ab7-75478400100d-000000@eu-west-1.amazonses.com> <20230508194748.6ydbfiozcfsynaq6@awork3.anarazel.de> <01020187fd0bfd45-d1609aba-f3c9-487a-b993-aac47f3f848a-000000@eu-west-1.amazonses.com> <20230508210400.ke4n5flpaxljtchd@awork3.anarazel.de> <20230509004637.cgvmfwrbht7xm7p6@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="lyf7a3datmmm42jg" Content-Disposition: inline In-Reply-To: <20230509004637.cgvmfwrbht7xm7p6@awork3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --lyf7a3datmmm42jg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, On 2023-05-08 17:46:37 -0700, Andres Freund wrote: > My current gut feeling is that we should use datconnlimit == -2 to prevent > connections after reaching DropDatabaseBuffers() in dropdb(), and use a new > column in 16, for both createdb() and dropdb(). Attached is a rough prototype of that idea (only using datconnlimit == -2 for now). This would need a fair bit more polish. The tests are crappy and output stuff to stderr and don't validate enough. The error messages are bad. No docs changes. More comments about why datconnlimit == -2 is used. Etc. But I think it should be sufficient to discuss whether this is a viable path. I guess we need to move this to -hackers. Perhaps I'll post subsequent versions below https://www.postgresql.org/message-id/20230314174521.74jl6ffqsee5mtug%40awork3.anarazel.de ? Greetings, Andres Freund --lyf7a3datmmm42jg Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v1-0001-Handle-interrupted-DROP-DATABASE.patch"