MIME-Version: 1.0
References: <611536258.144285.1740484963829.ref@mail.yahoo.com> <611536258.144285.1740484963829@mail.yahoo.com>
In-Reply-To: <611536258.144285.1740484963829@mail.yahoo.com>
From: o1bigtenor <o1bigtenor@gmail.com>
Date: Tue, 25 Feb 2025 06:39:11 -0600
Message-ID: <CAPpdf5-3fj-JCmQesVJoqdRO_Anab+usxMpnsuFGeXrZu_9uSw@mail.gmail.com>
Subject: Re: Corruption of few tables
Cc: Pgsql-general <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAPpdf5-3fj-JCmQesVJoqdRO_Anab%2BusxMpnsuFGeXrZu_9uSw%40mail.gmail.com>
Precedence: bulk

On Tue, Feb 25, 2025 at 6:03=E2=80=AFAM sivapostgres@yahoo.com
<sivapostgres@yahoo.com> wrote:
>
> Hello,
>
> Using PostgreSQL 11.11, compiled by Visual C++ build 1914, 64-bit  with P=
owerbuilder
>
> Recently, in one of our customers' places, we got an error while saving a=
 record from our custom-built application using PowerBuilder.     While sav=
ing a record, we compare a value from a table with a hard-coded value in ap=
plication.  Here the select command failed to fetch that particular record =
from the table and so the save failed.
>
> When we tried to read data from randomly selected tables [ from PGAdmin],=
 we found that records could not be read from a set of consecutive tables. =
We re-started server [ Windows Server 2012 ] and tried again to read those =
tables.  This time the failure was with only one table and select was succe=
ss in all other tables.
>
> So we dropped that particular table [ around 33000 records ], after remov=
ing all foreign key links and re-created that table and inserted all record=
s from a backup set.
>
> The problem got solved.  Since this is not the first time, we are getting=
 this error, I want to know
>
> 1.  Why is corruption happening?  How to find out the reason?
> 2.  What should I do to prevent this from happening again?
>
> Any steps or suggestions to avoid such corruptions is really appreciated.
>
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.

HTH