From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Use of non-restart-safe storage by temp_tablespaces |
Date: | 2017-05-29 19:08:55 |
Message-ID: | CAGTBQpaGTvHCHZU9cKYw+tBrKTn0wmCa4fyHJPRSRs700CXdCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 29, 2017 at 3:53 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Right now we don't document that temp_tablespaces can use
> non-restart-safe storage, e.g. /tmp, ramdisks. Would this be safe?
> Should we document this?
I have set up things like that, but it's nontrivial.
Just pointing the tablespace to non'restart'safe storage will get you
an installation that fails to boot after a restart, since there's a
tree structure that is expected to survive, and when it's not found,
postgres just fails to boot.
Or just use the tablespaces, I forget which. But in essence, it won't
do to do just that. What I ended up doing was backing up the empty
tablespace and adding a restore to system bootup scripts, so that
after a restart postgres finds an empty tablespace there.
So, there's a lot of internal hackery to document if you'd like to
document that kind of usage.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-05-29 19:14:07 | Re: psql: Activate pager only for height, not width |
Previous Message | Andres Freund | 2017-05-29 18:59:28 | Re: logical replication busy-waiting on a lock |