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 1rGLgB-00EqNu-Ag for pgsql-general@arkaria.postgresql.org; Thu, 21 Dec 2023 16:13:47 +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 1rGLg9-00BIkP-VQ for pgsql-general@arkaria.postgresql.org; Thu, 21 Dec 2023 16:13:45 +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.94.2) (envelope-from ) id 1rGLg9-00BIkH-4D for pgsql-general@lists.postgresql.org; Thu, 21 Dec 2023 16:13:45 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rGLg6-00BWcS-BJ for pgsql-general@lists.postgresql.org; Thu, 21 Dec 2023 16:13:43 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id B4B143200AEE; Thu, 21 Dec 2023 11:13:40 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 21 Dec 2023 11:13:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1703175220; x=1703261620; bh=AXPyFTFtlBA1nEh0r9LvSFBgvFfVNHBk/DFSPyW9DWw=; b= m3MCOtQMUboJZdGX+h7AG1XhUX+bmcU0oXDC9HCohpLKzbxGbfqkefET5K6BPrg2 5fFNyi/N010kYO4c8RVbBjizjqW3Niy9YEwGZaSEVLDHxNu6b+ibHNA/LLwY0alo oeIRKySr3CZwMPsYkVlBFWtbiTv0cMwMjcPIpVhv/q5g5ad4U14L53aiUrqL+UxV Bvdt5lUPDD5ncYgts6UJTg4UGMjZsyg7TY9hiRZ/0AKbjXgLqogEOtKNbTotUYit FpNoTbyQI4a96kLUZH+sRNN2c56A49xwFfDiCq1CYDuckcbEeXayPMuindHyjN/5 +F74wYDY11RKhbzn1YIg0g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1703175220; x= 1703261620; bh=AXPyFTFtlBA1nEh0r9LvSFBgvFfVNHBk/DFSPyW9DWw=; b=o OPS2NTVbrnqQOjySDhF8CkuHNnhoMdOBDhADsVab0qY/xGJ9rvoHeVE90gKsGhqj Hfj8MPP7vIyh/KaKL3vzB+h4TFne1CO8WIiW5F/SNojw+CfRhAfy0+A6kyCVUfGN 5bOhMYuB2yDbiI+0ACI873tgM6/ViHPxogISmOjUuoHUAHtnRIjjAKtw7/kEtt2B gRdsAv6x5ac/N/X/lw2l6PgzI+PA/qdR3sW/dfp035Cs5UOw0fwTJcBQgesyhAla hX9yiLdTCOg4R1Cr4VFMhrjBLft6egF0Ydjb5IFHOKOsmDRoNb28yvMESDLw7wzx /GZ+F8T+HuSWe6/4fph3w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdduhedgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeeivdfhieehheegueeileejieettdejhedugeefleek vdelkeehtdfgiefffeekudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 21 Dec 2023 11:13:39 -0500 (EST) Message-ID: Date: Thu, 21 Dec 2023 08:13:38 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Help understanding server-side logging (and more...) To: Dominique Devienne , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/21/23 03:05, Dominique Devienne wrote: > If by any chance, anyone has seen this kind of behavior before, in a > similar context or not, and has suggestions > on how we could further troubleshoot this (on the PostgreSQL > server-side, but also the Node.JS client-side, why not), > that would be greatly appreciated. 1) It would be helpful to add the Postgres version to any future posts. 2) Also more information on what this "They run PostgreSQL in a Linux container" means? > > Thanks, --DD > -- Adrian Klaver adrian.klaver@aklaver.com