Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vprfn-000If8-26 for pgsql-admin@arkaria.postgresql.org; Tue, 10 Feb 2026 17:37:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vprfm-000GN4-2V for pgsql-admin@arkaria.postgresql.org; Tue, 10 Feb 2026 17:37:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vprfm-000GMu-1P for pgsql-admin@lists.postgresql.org; Tue, 10 Feb 2026 17:37:15 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vprfl-00000001ToK-2HPH for pgsql-admin@lists.postgresql.org; Tue, 10 Feb 2026 17:37:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 61AHb8hv3869954; Tue, 10 Feb 2026 12:37:08 -0500 From: Tom Lane To: Scott Ribe cc: Pgsql-admin Subject: Re: debug a lockup In-reply-to: <62854B1F-FE6F-47BD-8B8C-5BEAA33EE3AD@elevated-dev.com> References: <62854B1F-FE6F-47BD-8B8C-5BEAA33EE3AD@elevated-dev.com> Comments: In-reply-to Scott Ribe message dated "Tue, 10 Feb 2026 09:55:55 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3869952.1770745028.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Feb 2026 12:37:08 -0500 Message-ID: <3869953.1770745028@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Scott Ribe writes: > Any way to introspect the current non-debug build to get a clue what's g= oing on in there? Backend stack traces taken with gdb should yield at least some clue even if you don't have debug symbols. regards, tom lane