From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Use of non-restart-safe storage by temp_tablespaces |
Date: | 2017-05-31 11:53:53 |
Message-ID: | CA+Tgmoa=Aex5Usgh9kw5UYrChQwA_Sh2znROcUA2-uT_vEYcyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 30, 2017 at 6:50 PM, Mark Dilger <hornschnorter(at)gmail(dot)com> wrote:
>> On May 29, 2017, at 11:53 AM, 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?
>
> The only safe way to do temporary tablespaces that I have found is to extend
> the grammar to allow CREATE TEMPORARY TABLESPACE, and then refuse
> to allow the creation of any non-tempoary table (or index on same) in that
> tablespace. Otherwise, it is too easy to be surprised to discover that your
> table contents have gone missing.
I think this would be a sensible approach.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | tushar | 2017-05-31 11:54:35 | Error while creating subscription when server is running in single user mode |
Previous Message | Christoph Berg | 2017-05-31 09:43:38 | Re: [HACKERS] [PATCH] relocation truncated to fit: citus build failure on s390x |