| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: database corruption |
| Date: | 2016-02-12 14:28:52 |
| Message-ID: | 20160212142852.GE60681@crankycanuck.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)crankycanuck(dot)ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2016-02-12 15:05:22 | Re: Test CMake build |
| Previous Message | FarjadFarid(ChkNet) | 2016-02-12 14:06:54 | Re: 9.4 -> 9.5 dump size reduction |