Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces
Date
Msg-id 20170606023417.GB14212@momjian.us
Whole thread Raw
In response to Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces  (Jerry Sievers <gsievers19@comcast.net>)
Responses Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Jun  5, 2017 at 04:38:32PM -0500, Jerry Sievers wrote:
> The SAN snaps capture the entire pgdata and WAL pg_xlog area but there
> is no attempt to copy the NVME device when the snaps are made.
> 
> There's an event trigger plus batch job now running tou avoid this risk.
> 
> We realize too that there are implications here if a backup is
> instantiated and PITR is done.
> 
> Just FYI that there could be others running like this ignorant of the
> potential gotchas.

Yes, if we implement the TODO you will create a TEMPORARY tablespace
that can't contain non-temporary and/or non-unlogged tables.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Why does logical replication launcher setapplication_name?
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces