| From: | Dimitrios Apostolou <jimis(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | having temp_tablespaces on less reliable storage |
| Date: | 2025-07-10 17:58:03 |
| Message-ID: | 1de78bf7-940a-9be5-e98d-a11f02d9e898@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-07-10 18:04:35 | Re: having temp_tablespaces on less reliable storage |
| Previous Message | abrahim abrahao | 2025-07-10 17:33:21 | Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin |