Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces |
Дата | |
Msg-id | AD2B68C8-1CE2-46FD-9905-4B8A9FC1A06B@anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Use of non-restart-safe storage by temp_tablespaces
|
Список | pgsql-hackers |
On May 29, 2017 12:15:37 PM PDT, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: >Claudio Freire wrote: >> On Mon, May 29, 2017 at 3:53 PM, Bruce Momjian <bruce@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. > >I think it'd be smart to support the use case directly, because there's >interest in it being actually supported (unlike the statu quo). >Something like restoring the tablespace to the empty state on boot, if >it's known to need it. Has the danger of making recovery harder after a restart where somebody forgot to mount some subdirectory ... Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-hackers по дате отправления: