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 1tnK4a-004Ew0-1I for pgsql-general@arkaria.postgresql.org; Wed, 26 Feb 2025 16:15:48 +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 1tnK4Y-008sFh-K4 for pgsql-general@arkaria.postgresql.org; Wed, 26 Feb 2025 16:15:46 +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 1tnK4Y-008sFI-9h for pgsql-general@lists.postgresql.org; Wed, 26 Feb 2025 16:15:46 +0000 Received: from fhigh-a6-smtp.messagingengine.com ([103.168.172.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tnK4V-000EC9-0v for pgsql-general@postgresql.org; Wed, 26 Feb 2025 16:15:45 +0000 Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id 8E6BA114016A; Wed, 26 Feb 2025 11:15:42 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Wed, 26 Feb 2025 11:15:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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=fm3; t=1740586542; x=1740672942; bh=Uw8D+uqu1rI/7i9FFl1NFOiEfvbxSiJBLrY8o6mbA1g=; b= WN8NYriAsyllBVjfTMtRtMwxYrsxid/UMDPih+AldBfipM7LO9eNpemsXcKY9rGH t2p8q2sdoH6bLl6OaSWC+ByNLTTOrayQmZLe399DUkdakj+BekhNHBkgbzznCEn6 YOHYY/BjPWhJWuqgrMb8h2/irXc6Oeff7RY9SAwyuoM8lc760Yk+ek13nbjabKro dKhZ3QBdsEZEP/eTFqzytCbcAH9gJv8n22vuozKuNevMAtLwc5y9Tklj40UHYTzB SnqdFbqxrEy+brwJExyNMG3PG9HL1cleoHKAoUyg/c56LYbbuGiovpH4HK52Or8d 24WAwJ4Chx3DdW28vR/fHA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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-sender:x-me-sender:x-sasl-enc; s=fm1; t=1740586542; x= 1740672942; bh=Uw8D+uqu1rI/7i9FFl1NFOiEfvbxSiJBLrY8o6mbA1g=; b=W 8uk3rktMjJ7eJm1mn2ng36OMOc/2Vhp/X523M1KO4Jw+cBmkXUOjLqKp0UgYlDCT jJKrdRgXj/dwR6fHrdIfXdk8veAQEoUxlTy0G7XlpTonUB/UT9OHUfPKzdfxvIR5 wR5coni7g6JJ9fwyfEqeqmptkuh3et6PR0bd0BVhCVgUKff000D1qckzA30fSHX0 bC+J8iDD+ggBLi/AREt1ex948YZy2eTXuLAgK6D01ciwtOWL3/Zxmzsz6PxdfE2z T5tg6A4t/RFz5GIJSdV2cp/pISOJUpr/DxoLDbsmQdL7PcFdNRG1I+D1e24oxqzo 7+qHfHI+3XRdVcSnw7s6Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdekhedtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgg gfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghv vghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrf grthhtvghrnhepgfdufeekhfevfeelveeiueevhedvuddukeduvddvlefhueeuieejtdeu vdevvdeunecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghv vghrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopeefpdhmohguvgepshhmth hpohhuthdprhgtphhtthhopehsihhvrghpohhsthhgrhgvsheshigrhhhoohdrtghomhdp rhgtphhtthhopehoudgsihhgthgvnhhorhesghhmrghilhdrtghomhdprhgtphhtthhope hpghhsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 26 Feb 2025 11:15:41 -0500 (EST) Message-ID: Date: Wed, 26 Feb 2025 08:15:41 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Corruption of few tables To: "sivapostgres@yahoo.com" , o1bigtenor Cc: Pgsql-general References: <611536258.144285.1740484963829.ref@mail.yahoo.com> <611536258.144285.1740484963829@mail.yahoo.com> <4536e07d-b846-4965-b0b1-e384b4915513@aklaver.com> <595456242.3981765.1740551787912@mail.yahoo.com> <38220057.102774.1740554474431@mail.yahoo.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <38220057.102774.1740554474431@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/25/25 23:21, sivapostgres@yahoo.com wrote: > Since we rectified the issue in ver 11, I couldn't get more details. What issue is this?: ls_pack_version <> ls_db_version or the SSL issue you show below? > > Now we are getting the same [ or similar ] issue in PostgreSQL 15.7 > (Ubuntu 15.7-1.pgdg24.04+1) on x86_64-pc-linux-gnu, compiled by gcc > (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit > > When we ran the following query, in PGAdmin Is this all on one machine, between machines on same network, machines on different networks? What version of pgAdmin? What if you use psql? > > Select releasenumber, buildnumber > From   public.co_version > Where  modulename = 'ALL'; > > We got the following error > ERROR: SSL error: bad length > SSL SYSCALL error: No error (0x00000000/0) > > When we try to run the same above query by opening another window [ same > PGAdmin, in another window ], we get correct expected result and NOT the > error. > > Couldn't identify whether this is related to network or corruption. > > Happiness Always > BKR Sivaprakash > > On Wednesday 26 February, 2025 at 12:07:00 pm IST, > sivapostgres@yahoo.com wrote: > > > Yes, we are planning to upgrade to Ver 17 soon. > Yesterday, we got the similar error in one more client place where > version 15 is running in Ubuntu Server.   We are trying to figure out > whether it's a network issue or corruption issue. > > On Tuesday 25 February, 2025 at 08:24:44 pm IST, Adrian Klaver > wrote: > > > On 2/25/25 04:39, o1bigtenor wrote: > > On Tue, Feb 25, 2025 at 6:03 AM sivapostgres@yahoo.com > > > > Not really a direct answer - - - but - - - have you considered > > updating Postgresql. > > Version 11 was EOL (end of life) over a year ago. Version 17 according > > to the charts I've found > > is the current version. > > Actually the current community supported versions are 13-17. > > The time lines for support can be found here: > > https://www.postgresql.org/support/versioning/ > > > > > > > HTH > > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > > > -- Adrian Klaver adrian.klaver@aklaver.com