| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Use of non-restart-safe storage by temp_tablespaces |
| Date: | 2017-06-06 02:34:17 |
| Message-ID: | 20170606023417.GB14212@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-06 02:38:43 | Re: Use of non-restart-safe storage by temp_tablespaces |
| Previous Message | Peter Eisentraut | 2017-06-06 02:31:00 | Re: Why does logical replication launcher set application_name? |