On Fri, Feb 12, 2016 at 07:46:25AM -0500, Bill Moran wrote:
> Long term, you need to fix your hardware. Postgres doesn't corrupt
> itself just because the disks fill up, so your hardware must be lying
> about what writes completed successfully, otherwise, Postgres would
> be able to recover after a restart.
It may not be the hardware. Depending on how vmware is configured, it
could just be a setting. Also, something in the OP's message made me
think that this was _actually_ a network-attached disk, which can also
have such problems. (But in general, I agree.)
A
--
Andrew Sullivan
ajs@crankycanuck.ca