Thread: having temp_tablespaces on less reliable storage

having temp_tablespaces on less reliable storage

From
Dimitrios Apostolou
Date:
Hello list,

I have a database split across many tablespaces, with temp_tablespaces
pointing to a separate, less reliable device (single local NVMe drive).
How dangerous is it for the cluster to be unrecoverable after a crash?

If the drive goes down and the database can't read/write to
temp_tablespaces, what will happen?

If I then configure temp_tablespaces to point to a working location, would
that be enough to start the cluster? Or other bad things can happen?

Can't find any related documentation, but I expect loss of "temp" space is
of minor importance.

Thanks in advance,
Dimitris




Re: having temp_tablespaces on less reliable storage

From
"David G. Johnston"
Date:
On Thu, Jul 10, 2025 at 10:58 AM Dimitrios Apostolou <jimis@gmx.net> wrote:
Can't find any related documentation, but I expect loss of "temp" space is
of minor importance.

You might want to try finding some old discussions about why putting temp tablespace on a RAM-drive is not a supported configuration.

David J.