Anyway, from this POV all we really need to know is that the device
hosting this tablespace failed to mount when the machine was rebooted,
and then postgres restarted.
Good to know postgresql had nothing to do with the missing data. I
wasn't sure if it was user error, config problem or hardware.
From my experience, it doesn't really matter if you have a
sophisticated SAN or put together an ad-hoc nas/das solution, storage
likes to bite you. The only thing that helps me sleep at night is sound
replication and backups (in some cases triple redundancy with aging data
sets).
Andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
