How does Postgres atomically updates secondary indices?

Question

I understand that when a transaction performs a change, Postgres mvcc scheme stores a new row with the updated data, and an associated version.

Other transactions kno