Reason for using write barrier before unlocking the buffer header in Postgresql
Without looking at the code, that seems not surprising to me: if you have the buffer header locked and write to it, then you want all these writes to happen before you unlock the buffer, right?