> I'd guess it's probably more like option 3 - Glusterfs ate my database.
Hi, thanks for your reply! We do archive logs on a distributed Glusterfs volume in case the streaming replication gets too far behind and the transaction logs have been removed. Would a restore of a corrupt 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 changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
