Comment by ComputerGuru
10 hours ago
Another option would be a good way of placing indexes on a different physical disk. You could use fast, ephemeral storage like you can for a WAL without amplifying the writes to the same device that is your expensive bottleneck. You could rebuild on data loss.
But it would add complexity to detect out-of-sync indexes and tables.
You mean tablespaces: https://www.postgresql.org/docs/current/manage-ag-tablespace... ?
Maybe? I wasn’t under the impression these could be reliably lost or out of sync without risking data loss?
Wasn't aware you could put a WAL on a unreliable storage system either without risking data loss?
Would be interesting for indexes say put them on ram drive and rebuild them on restart if they aren't there just fallback to table scans.
MSSQL has memory optimized tables that do this sort of thing: https://learn.microsoft.com/en-us/sql/relational-databases/i...
3 replies →