3 ms·
> 3. Tiered storage. Do you mean tablespaces? https://www.postgresql.org/docs/10/manage-ag-tablespaces.html https://www.postgresql.org/docs/10/manage-ag-tables
by eitland 5y ago
> 3. Tiered storage.
Do you mean tablespaces? https://www.postgresql.org/docs/10/manage-ag-tablespaces.html https://www.postgresql.org/docs/10/manage-ag-tablespaces.htm...
They'll allow you to have some parts on database on faster devices for instance.
- vaughan 5y agoVery cool - I had no idea this existed. I wonder if this could be useful for using ramdisks when working with temp tables.
- eitland 5y agoVery possible. I learned about the possibility a good decade ago when working on Oracle. For high performance use we used to have two areas: - one small SSD-backed area where new inserts happened (Server class SSD was new and relatively expensive back then.) - one (or more) areas for permanent storage, based on ordinary disks with good storage/price Then we had processes that processed data from the SSD Pool and wrote them to long term storage asynchronously. Edit: I should say I was very happy to find the same feature on Postgres, Oracle is a real hassle in more than one way.
- jatone 5y agoyes, ramdisks are great. =) I've used that approach to replace redis with a faster version on postgres. =)
- zinclozenge 5y agoThat does seem neat, but I was actually thinking more like off-loading cold data to S3, or some such. Maybe even having distinctions between (ultra) hot, warm, cold data.