| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org,Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>,Claudio Freire <klaussfreire(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-29 19:24:43 |
| Message-ID: | AD2B68C8-1CE2-46FD-9905-4B8A9FC1A06B@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 29, 2017 12:15:37 PM PDT, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>Claudio Freire wrote:
>> 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.
>
>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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sven R. Kunze | 2017-05-29 19:25:00 | Re: Surjective functional indexes |
| Previous Message | Andres Freund | 2017-05-29 19:23:04 | Re: logical replication busy-waiting on a lock |