From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, 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:41:08 |
Message-ID: | 20170606024108.GC14212@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 5, 2017 at 07:38:43PM -0700, Andres Freund wrote:
> On 2017-06-05 22:34:17 -0400, Bruce Momjian wrote:
> > 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.
>
> FWIW, allowing UNLOGGED tables, rather than just TEMPORARY ones,
> increases the complexity of that project noticeably. For TEMPORARY you
> basically don't need to do much but to recreate the structure inside the
> tablespace at start - fairly simple. But for UNLOGGED you need to find
> a way to recreate the relevant file and init forks - otherwise we might
> not notice what needs to be reset at a crash restart, and we might error
> out when executing selects etc. and then the table's not there.
> Presumably recreating files & init forks that at first table access is
> doable, but it's not entirely trivial to do locking wise.
Agreed, that is why they are separate adjacent items on the TODO list.
:-)
--
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 | Hao Lee | 2017-06-06 02:44:03 | Re: Do we need the gcc feature "__builtin_expect" to promote the branches prediction? |
Previous Message | Andres Freund | 2017-06-06 02:38:43 | Re: Use of non-restart-safe storage by temp_tablespaces |