|
|
|
|
|
|
by anarazel
3360 days ago
|
|
|
> Write amplification is a result of PostgreSQL's decision to not used clustered indexes, there's not much that can be done to avoid it without a massive redesign of the storage engine I don't think that's entirely accurate - the issue is more that indexes contain pointers to the heap position (simplified) of a tuple, rather than being indirect and pointing to the primary key, which then is resolved by another index (be that clustered / primary or not). Updates already don't have to update indexes iff none of the indexed columns change (HOT - Heap-Only-Tuples). The proposed change (WARM - write amplification reduction method), allows to avoid updating indexes on non-changing columns, even if other indexes change. https://www.postgresql.org/message-id/CABOikdMNy6yowA+wTGK9R... > In all reality though, Uber wanted a key-value store and not an RDBMS Agreed on that. |
|
|