> If it's just storing the logs, I doubt it's the cause of the problem. You can
> ignore my message. I had too much fun fighting with Gluster recently.
Hehe, hope you came through on top ;). Anyways, I added an md5sum calculation
in the archiving script just to be able to verify that the files d
archived log file give the symptoms we are seeing?
Would not Postgresql detect that the logfile was corrupt?
Are there some way I can analyze archived logs files to see if this is the
problem?
Regards
Lars Arvidson
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
only have one log row and that
looks similar to the other once and it was triggered by an insert "ERROR: could
not read block 2023 in file "base/16390/22841": read only 0 of 8192 bytes". The
offending file was an index. This problem was fixed with a VACCUM FULL on the
table
