Search Postgresql Archives

Re: Corruption of few tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 25, 2025 at 6:03 AM sivapostgres@xxxxxxxxx
<sivapostgres@xxxxxxxxx> 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 PowerBuilder.     While saving a record, we compare a value from a table with a hard-coded value in application.  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 success in all other tables.
>
> So we dropped that particular table [ around 33000 records ], after removing all foreign key links and re-created that table and inserted all records 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






[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux