Re: OK to put temp tablespace on volatile storage or to omit it from backups? - Mailing list pgsql-general

From Christophe Pettus
Subject Re: OK to put temp tablespace on volatile storage or to omit it from backups?
Date
Msg-id B9E10DDA-F3A9-403B-BBEF-E94F777248FA@thebuild.com
Whole thread Raw
In response to Re: OK to put temp tablespace on volatile storage or to omit it from backups?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Apr 30, 2013, at 8:13 PM, Tom Lane wrote:

> Appears to be sheer blather, or at least not tempered by any thoughts
> of whether it'd work in special cases.

As the author of that blog post, I'd go with option (b).  :)  And that lack of tempering was actually the point.

The point there was that having the tablespace directories disappear shouldn't be considered a normal operational
model. (Like, for example, putting a tablespace in a RAM disk.)  There's no question that you can patch the database
backtogether if the underlying storage of a tablespace disappears, but that should be thought of as disaster recovery,
notas a "oh, third time this week" operation. 

--
-- Christophe Pettus
   xof@thebuild.com



pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Simple SQL INSERT to avoid duplication failed: why?
Next
From: Christophe Pettus
Date:
Subject: Re: OK to put temp tablespace on volatile storage or to omit it from backups?