In Azure there are VMs that have local storage either as spinning disk (A-series) or SSD (D-series). Considering this space is wiped on reboot…
- Is there a benefit to choosing the SSD option for PostgreSQL?
- Can it be configured to use for temp/swap data even though it’s wiped on reboot?
- How would one need to condition this disk space before PostgreSQL’s start?
I think it’s worth noting (based on comment) that the install and application databases won’t be installed on the local storage (which are wiped)… I’m only curious if there are bits that could take advantage of it (temporary databases/tables, swap space, etc) and what would need to be configured to initialize/re-initialize any directories that would/could be used as such.
The same questions that would apply if one were to have say a RAM-Drive (that is not permanent).