| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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:15:37 |
| Message-ID: | 20170529191537.bs654gil2qsl2krk@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-05-29 19:21:50 | Re: logical replication busy-waiting on a lock |
| Previous Message | Jeff Janes | 2017-05-29 19:14:07 | Re: psql: Activate pager only for height, not width |