From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
---|---|
To: | Kevin Brannen <KBrannen(at)efji(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Temporary tablespaces on a RAM disk |
Date: | 2020-03-17 19:28:03 |
Message-ID: | ZR0P278MB0028E026FF7433F72BD82C08D2F60@ZR0P278MB0028.CHEP278.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Daniel Westermann 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.
>Well, we point our "stats_temp_directory" to a tmpfs partition, which is probably fairly common (or so I'd guess).
>But a full tablespace with tables and everything? That sounds pretty risky for anything other than a place to store
>data for transformation or summary of data that could be recreated by restarting a process if the server goes down
>in the middle.
>I think you'd be better off explaining what your goal is and then people could give you better comments.
Thank you for the hint with stats_temp_directory. I am only talking about temp_tablespaces which are supposed for temporary objects only. It is pretty clear not to use that for persistent objects, I know.
Regards
Daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Westermann (DWE) | 2020-03-17 19:33:59 | Re: Temporary tablespaces on a RAM disk |
Previous Message | Daniel Westermann (DWE) | 2020-03-17 19:26:36 | Re: Temporary tablespaces on a RAM disk |