hard20 pts · first answer countstransactionspostgresqlrow-locks

SELECT FOR UPDATE creates WAL

A read-heavy job in PostgreSQL runs SELECT ... FOR UPDATE on 10 lakh rows but changes nothing. Monitoring shows lots of WAL and dirty pages. Why?

A.Row locks are stored in the row header, which is writtenB.FOR UPDATE copies each row into a temp tableC.The planner writes stats for each locked rowD.Locks are written to the WAL only on replicas

Discussion 0

Join free to post in the discussion.

SELECT FOR UPDATE creates WAL

Discussion 0

Related questions