Low-level Postgres internals piece that instantly makes row locks more concrete.
boringsql.com/posts/row-locks-on-th…
boringsql.com
Where PostgreSQL stores row locks
What SELECT FOR UPDATE, FOR SHARE, and a foreign key check actually write into the tuple header. t_xmax as a locker, the infomask bits that say so, MultiXactIds when two sessions lock the same row, and the pg_multixact files that grow behind them.