From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Temporary tablespaces on a RAM disk |
Date: | 2020-03-17 17:59:57 |
Message-ID: | 427c0a2d-77aa-d931-3738-0128a069c2df@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/17/20 12:19 PM, David G. Johnston wrote:
> On Tue, Mar 17, 2020 at 2:49 AM Daniel Westermann (DWE)
> <daniel(dot)westermann(at)dbi-services(dot)com
> <mailto:daniel(dot)westermann(at)dbi-services(dot)com>> wrote:
>
> is someone using temporary tablespaces on a RAM disk ? Any experiences
> with that?
> I did some quick tests and checked the archives but could not find any
> information that either confirmed it is a bad idea nor the opposite.
>
>
> There is a nice big bold warning callout in the documentation that covers
> this explicitly.
>
> https://www.postgresql.org/docs/12/manage-ag-tablespaces.html
Warning
Placing a tablespace on a temporary file system like a RAM disk risks the
reliability of the entire cluster.
But aren't temporary files removed when you restart Postgres? (I'm assuming
that temp_tablespaces is treated "the same" as data/pgsql_tmp. Is that a
false assumption?)
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-17 19:22:07 | Re: Temporary tablespaces on a RAM disk |
Previous Message | David G. Johnston | 2020-03-17 17:19:02 | Re: Temporary tablespaces on a RAM disk |