Hi čt 20. 8. 2026 v 18:52 odesílatel Bruce Momjian <[email protected]> napsal:
> On Sun, Jul 12, 2026 at 08:48:28PM +0200, Pavel Stehule wrote: > > Hi, > > > > My customer reported corrupted toast tables on PostgreSQL 14.20. He uses > wal > > archiving - so it was possible to read data from broken pages. The > corrupted > > rows are detected by SELECT command. > > I would first look to see if it was fixed from 14.20 to 14.24. > Unfortunately I am not able to check this. The customer reported this issue only once. Now, he did upgrade, and he didn't report this issue again. We didn't find any way how this issue can be reproduced. We manually executed VACUUM on the database that was restored to the time close before this issue - and the data was not broken - but now, I am not sure what was the minor version that we used for this test (we did these tests a few months after this issue). I am almost sure this bug has ultra low frequency - but not zero - and probably there are more different reasons with the same error message at the end. Regards Pavel > -- > Bruce Momjian <[email protected]> https://momjian.us > EDB https://enterprisedb.com > > Do not let urgent matters crowd out time for investment in the future. >
