3 ms·
> I think because Postgres writes the entire row even if a single column has been updated. You might want to have a look at HOT [0] tuples if you haven't alrea
by hgamaral 4y ago
> I think because Postgres writes the entire row even if a single column has been updated.
You might want to have a look at HOT [0] tuples if you haven't already.
[0] - https://www.cybertec-postgresql.com/en/hot-updates-in-postgresql-for-better-performance/ https://www.cybertec-postgresql.com/en/hot-updates-in-postgr...
- madjam002 4y agoThanks for the pointer, that looks very interesting!
- jpgvm 4y agoIf you want to do writes without a ton of amplification on PG this is the only way right now. Eventually maybe PostgreSQL will get a second storage engine that uses an undo log instead, like the somewhat stalled zheap effort for instance. That said the numbers of rows you are talking about are easy peasy for PostgreSQL.
- blast 4y agoThanks. I also found https://medium.com/adyen/fighting-postgresql-write-amplification-with-hot-updates-c8090f329ad6 https://medium.com/adyen/fighting-postgresql-write-amplifica....