Scaling Postgres with Read Replicas and Using WAL to Counter Stale Reads
Wouldn't this only work when your client is the one that last updated the record? Because how else would you know the correct min lsn? Seems like you would need to store the map from user to lsn in something other than pg to get any benefit here.