So this does not affect SSI guarantees if the transactions involved all operate on the same row? Is my understanding correct?
For instance can I update a counter with serializable isolation and not run into this bug?
I think so, yeah. You could theoretically have a G2-item anomaly on a single key, but in PostgreSQL's case, the usual write-set conflict checking seems to prevent them.