Re: Temporary tablespaces on a RAM disk

From: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Temporary tablespaces on a RAM disk
Date: 2020-03-17 19:57:25
Message-ID: ZR0P278MB0028E380234DE3691D7DE7CFD2F60@ZR0P278MB0028.CHEP278.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Laurenz,

>From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
>Sent: Tuesday, March 17, 2020 20:50
>To: Daniel Westermann (DWE) <daniel(dot)westermann(at)dbi-services(dot)com>; pgsql-general(at)lists(dot)postgresql(dot)org <pgsql-general(at)lists(dot)postgresql(dot)org>
>Subject: Re: Temporary tablespaces on a RAM disk

>On Tue, 2020-03-17 at 09:49 +0000, Daniel Westermann (DWE) 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.

>Taking a step back, wouldn't it be better to increase "work_mem"
>and "temp_buffers" and set "temp_file_limit", so that temporary
>files are avoided whenever possible and temporary tables are cached?

I don't think you can avoid that for all cases, especially when working with large data sets. That was one of the reasons for my initial question.

>Then essentially you are using the same memory for the same purposes,
>but in a supported fashion.

Agreed.

Regards
Daniel

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2020-03-17 21:05:20 Re: Temporary tablespaces on a RAM disk
Previous Message Daniel Westermann (DWE) 2020-03-17 19:51:10 Re: Temporary tablespaces on a RAM disk