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.94.2) (envelope-from ) id 1uWtO1-002sw7-3G for pgsql-www@arkaria.postgresql.org; Wed, 02 Jul 2025 09:04:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uWtNz-00DSF0-6I for pgsql-www@arkaria.postgresql.org; Wed, 02 Jul 2025 09:04:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWtNy-00DSEm-Up for pgsql-www@lists.postgresql.org; Wed, 02 Jul 2025 09:04:11 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uWtNx-005GtL-1j for pgsql-www@lists.postgresql.org; Wed, 02 Jul 2025 09:04:11 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-32b2f5d91c8so33642741fa.0 for ; Wed, 02 Jul 2025 02:04:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1751447048; x=1752051848; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zFBUmFAWhhBeBhkmi5kcTOBQaZPbRkXPN4BBKtgTpjg=; b=EksjS5Eqi9Y9VLJ1NqoKCBW59xB1ndWc4f95nRFEyMRzX/8CiksPxG/+ktaMNRE7jj Uz57Jpmuaw9qyyUTFfPkyFB5YFFq42LTfP/ZMjytB2Xtm8etOeS1A6z15gX4lkRzrAXw 3J2wbHDzcP7/yRqu+ngX5tmdr1iUH+7w/bBDLyA1gG2XNAvmOqVKgUudZaHaiPmrq67j clCGlWUbrHYSO4TiqSda6iHkkI+B27YjOkZsWkoILNTVHsBXWmXsKzNOXn4z4w0pEEhR WR8cNBxLQbd/hepoc2JQDa9Qsrn8YQytDgcXSNTU77YOMKPgnCsK8bCItGSOT6vjti08 tQkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751447048; x=1752051848; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zFBUmFAWhhBeBhkmi5kcTOBQaZPbRkXPN4BBKtgTpjg=; b=XvbgqPiLbqe+XbCe180LCZdnQQa6DpOK8JV5E5KWItTtUNC2L2WnAjr4elcvg8Q+PC DwLs3EUsKA6MgFPnAThPS7rPlGWiAX0s/3BBQg9F6+OJElf/svi6hUv81skVk8lx/m4A eQZG44ZQIt/fVCozi8i+COVD22H4Oc8ujzEZMNF6cfSk4dQ5Yoye5OfF2+07QbVIvj/9 JtBm6sqUky5Usbhd/amQf6HlXcjnALr0WPDl7dCOLJExsDUFhV61NRva2C54JPikCCJh bbmyOhmG0WcEuFKLfIHUyhVTT+VIizwGL8EPwoMSMzqtlZzsHt24riN8FF+GSEYsCDf6 Z8ng== X-Gm-Message-State: AOJu0YwBcZM8n0NqEAuFnl1OBFZlZ0nbqdujl6NxQ1QaqnBBxxVF38yj FB4lnzeHDDGzc9zal7zx6xiZXBNAeI2uHHg9L4Hsm5lC/C/EfzTOx3O1PsPahEDq/TroMPTaaSO TtUcNPukqGvMed1N4QLudBL8I685aQIr2xW6nKpz6I6xzDGiGMpMoIxM= X-Gm-Gg: ASbGncue18Qbd5nTxEAmqjDRvoGaKe5k18qVuPTIpDrxyDPajdFP2SyvaIC+rygltEo cqc5sK1hHYUw7Mzmk0U/N+qpYgo8cPgPUbuf2Z+M4p+YB2bywmPXE4dE17pTvLJwmOIBY/tMhoi HR+qod3TYdMTWTdgwlyITmeVetDp5H7wEyF6/DXyxyASTZDx1DiXTjxMA= X-Google-Smtp-Source: AGHT+IGnta93Kfth3evQrYUP9OhFo+BmBfUPXMCgVYox36F6unuFRRbv0NC8JGmYk0iwSyIiU5KK+Ty7O7b1z878OTU= X-Received: by 2002:a2e:bc28:0:b0:32a:5fe2:81bf with SMTP id 38308e7fff4ca-32e00048fb9mr8095101fa.24.1751447048420; Wed, 02 Jul 2025 02:04:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jelte Fennema-Nio Date: Wed, 2 Jul 2025 11:03:57 +0200 X-Gm-Features: Ac12FXxu4WQh_hNrkuWTBB1M000IHQVp4srH0dcS0OVkMciQoFY7wfC2S2lb-2M Message-ID: Subject: Re: Cf app crashes To: Magnus Hagander Cc: PostgreSQL WWW Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2 Jul 2025 at 10:54, Magnus Hagander wrote: > > Hmm, are you saying you're changing something at the *source* of the calls? Surely the bug is in the code that curn the cf app as that's the one that crashdumps? Yes, but that's a more involved fix. So I wanted to do a quick hotfix instead. Can you forward one of the recent errors again? To be sure it's actually the same one still.