On Mon, May 29, 2017 at 3:53 PM, Bruce Momjian <br...@momjian.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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
