On 2/25/25 23:21, sivapostg...@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.p
On 2/25/25 22:33, sivapostg...@yahoo.com wrote:
Thanks
// Following is the PB code to retrieve data
ls_pack_version = fn_get_product_version()
ls_pack_build = fn_get_product_build()
Select releasenumber, buildnumber
Into :ls_db_version, :ls_db_build
From public.co_version
Where modulena
On Wed, Feb 26, 2025 at 9:06 AM Greg Sabino Mullane
wrote:
> On Wed, Feb 26, 2025 at 2:21 AM sivapostg...@yahoo.com <
> sivapostg...@yahoo.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.
>
And it tak
On Wed, Feb 26, 2025 at 2:21 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.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
Since we rectified the issue in ver 11, I couldn't get more details.
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
Sel
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
Thanks
// Following is the PB code to retrieve data
ls_pack_version = fn_get_product_version()ls_pack_build =
fn_get_product_build()
Select releasenumber, buildnumber Into :ls_db_version, :ls_db_build From
public.co_version Where modulename = 'ALL'; If SQLCA.sqlcode <> 0 Then
ls_db_v
On 2/25/25 04:39, o1bigtenor wrote:
On Tue, Feb 25, 2025 at 6:03 AM sivapostg...@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.
On Tue, Feb 25, 2025 at 7:03 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
> 1. Why is corruption happening? How to find out the reason?
>
It sounds more like user error than actual corruption, but without more
data we cannot determine. Show us the exact commands you ran, along wit
On Tue, Feb 25, 2025 at 6:03 AM sivapostg...@yahoo.com
wrote:
>
> Hello,
>
> Using PostgreSQL 11.11, compiled by Visual C++ build 1914, 64-bit with
> Powerbuilder
>
> Recently, in one of our customers' places, we got an error while saving a
> record from our custom-built application using Power
Hello,
Using PostgreSQL 11.11, compiled by Visual C++ build 1914, 64-bit with
Powerbuilder
Recently, in one of our customers' places, we got an error while saving a
record from our custom-built application using PowerBuilder. While saving a
record, we compare a value from a table with a h
11 matches
Mail list logo
