| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | "sivapostgres(at)yahoo(dot)com" <sivapostgres(at)yahoo(dot)com> |
| Cc: | o1bigtenor <o1bigtenor(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corruption of few tables |
| Date: | 2025-02-26 14:06:08 |
| Message-ID: | CAKAnmmJRknWQBGUPj3XaAFv4i3YJ-Kg4TvgTVTLn3vuwWwM2+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 26, 2025 at 2:21 AM sivapostgres(at)yahoo(dot)com <
sivapostgres(at)yahoo(dot)com> wrote:
> issue in PostgreSQL 15.7
>
Still missing a ton of bug fixes - Postgres 15 is on version 15.12. Try to
get that upgraded.
> We got the following error
> ERROR: SSL error: bad length
> SSL SYSCALL error: No error (0x00000000/0)
>
This is a network error, not data corruption. How much time passes from
starting the query until you see the error? Make sure all your related
programs are up to date (esp. pgadmin, openssl). Check the Postgres logs to
see if there is more information or perhaps other information about why the
SSL connection is failing.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-02-26 14:28:57 | Re: Corruption of few tables |
| Previous Message | François Lafont | 2025-02-26 12:38:22 | PG16 and replication, ensure a clean switchover after a stop of the primary server |