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 1tEf6M-008tNc-Ms for pgsql-performance@arkaria.postgresql.org; Sat, 23 Nov 2024 01:38:22 +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 1tEf6J-00EJ9l-F7 for pgsql-performance@arkaria.postgresql.org; Sat, 23 Nov 2024 01:38:19 +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 1tEf6J-00EJ9c-1O for pgsql-performance@lists.postgresql.org; Sat, 23 Nov 2024 01:38:19 +0000 Received: from relay5-d.mail.gandi.net ([217.70.183.197]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEf6G-003Mum-3M for pgsql-performance@lists.postgresql.org; Sat, 23 Nov 2024 01:38:17 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 8CE9C1C0003; Sat, 23 Nov 2024 01:38:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1732325894; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u8cVECDMDuf4nPW09ctSgN+USWjMQjv8AJspiyhGbbA=; b=FZ7RKAXsg55nehgt31fJq0/iJ9G6Z0ZVu7Q0YhlPvdKGz0RlCYxdUDzPawtVTRRXLSrB3U hKmA9yfNvRSBLTtsWEGy8MVChovJmj3E9Dpfe2RPSQdMkYYj+EldCAWrPSzt53Gy3lkzFv kBPZm/CZKcbb322vljlYtRK7HL83mXAJGLxv+x2wAJQk/thmdrnJS7x5YIpSntlwzHRm+U gGDQmh+rE95iNyYFmudHluuxM+aJx/tXj1x0BLKy0DTZxUaWZVSg48CMfzu+ZIyrK5leAG opfE4exyydLs6vmyMaG+BBk61/rJY9aiKC62FDzcajxiO3/biJtdFb7V+WQl6g== Message-ID: <41089e4c-6959-4698-a49c-2f6d9231b330@vondra.me> Date: Sat, 23 Nov 2024 02:38:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: could not send data to client: Connection reset by peer To: James Pang , pgsql-performance@lists.postgresql.org References: Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/21/24 13:13, James Pang wrote: > experts, >    Postgresql v14.8,  client app use Postgresql JDBC, it start a single > query that return 470k rows totally in one time, but sometimes, database > server side got error "could not send data to client: Connection reset > by peer".  >    any idea why it faced this error?  > This means the TCP/IP connection got closed abruptly. It might be because the client had some issue, or something on the network path decided to block the connection (like a router or a firewall). regards -- Tomas Vondra