Re: Corruption of few tables - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Corruption of few tables
Date
Msg-id a1e695d0-1945-47c8-a9ff-eee14f1a1f30@aklaver.com
Whole thread Raw
In response to Re: Corruption of few tables  ("sivapostgres@yahoo.com" <sivapostgres@yahoo.com>)
List pgsql-general
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 <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 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 2/25/25 04:39, o1bigtenor wrote:
>  > On Tue, Feb 25, 2025 at 6:03 AM sivapostgres@yahoo.com 
> <mailto: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/ 
> <https://www.postgresql.org/support/versioning/>
> 
> 
>  >
>  > HTH
> 
>  >
>  >
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Corruption of few tables
Next
From: Adrian Klaver
Date:
Subject: Re: Ideas about presenting data coming from sensors