Re: Sensitivity to drive failure?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Israel Brewster <israel(at)ravnalaska(dot)net>
Cc: "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Sensitivity to drive failure?
Date: 2015-10-02 16:30:54
Message-ID: 22383.1443803454@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Israel Brewster <israel(at)ravnalaska(dot)net> writes:
> How sensitive is PostgreSQL to a failure that causes it to loose a single tablespace, while the rest of the database cluster is still accessible? Will it continue running, allowing access to databases that aren't in the missing tablespace, or will it crash (or similar)?

If the tablespace just disappears mid-run, things will not be good; any
dirty buffers for those tables that are hanging around in shared buffers
cannot be written out, so checkpoints cannot complete, so WAL will
accumulate indefinitely (meaning that crash recovery time will grow,
among other bad effects). It's not going to be any better than losing
some random subset of files that aren't separated by tablespace.

I don't recall the details for sure, but I think you could manually
recover from such a scenario by dropping all the affected tables. But
the tablespace mechanism, per se, doesn't help you in this. It's not
designed to be a robustness aid.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Olivier Dony 2015-10-02 16:44:55 Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
Previous Message Israel Brewster 2015-10-02 16:16:20 Sensitivity to drive failure?