Re: Temporary tablespaces on a RAM disk

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(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
Date: 2020-03-17 19:41:09
Message-ID: 19300.1584474069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> writes:
>> People have asked about this before, so maybe it'd be an idea to make
>> an explicit concept of a temp tablespace that only accepts temp tables,
>> and do whatever is needful to make that robust. But I've not heard of
>> any work towards that.

> That's what I thought temp_tablespaces are for ( plus sorts, temporary files getting created by materialized views ... )

No ... temp_tablespaces says it's okay to use any of the listed
tablespaces to keep temporary working files in, but it doesn't
say that those tablespaces can *only* be used for that.

The whole business of temp tables (as opposed to those invisible-to-SQL
working files) in such a tablespace is a separate issue, too. I think
that the server would mostly survive having temp-table files disappear
during reboot, but it's not an officially supported or tested scenario.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2020-03-17 19:50:56 Re: Temporary tablespaces on a RAM disk
Previous Message Daniel Westermann (DWE) 2020-03-17 19:33:59 Re: Temporary tablespaces on a RAM disk