How to properly organize concurrent data access?

Question

PostgreSQL

The bottom line is that the data can be edited by N users, but in fact the ideal option is that the one who first opened the record edits it, the rest can open the record only for viewing.
perhaps there is already such a bike (you can write your own, but I don’t think I’m the only one who has come across this), or perhaps there is a more correct solution and approach to this problem

Answer 1

We solved a similar problem as follows: We
created a table into which an object is entered when it is raised for editing. All other users, when trying to edit this object, receive a message that the user "such and such" is already editing it and the form rises in read-only mode.
When the first user closes the form with the object, the record is removed from the table and the object can be edited by another user.
Sometimes there were failures (for example, a disconnect) and the user who opened the object for editing could not correctly release the object being edited. In this case, if the object is in the editable table, but the process with its spid and username is not on the SQL server, we forcibly delete the object from the editable table.
Without such a mechanism, inconsistencies of the form were periodically scored: "I changed the object, saved it, raised it for viewing, and it's different."

Answer 2

The bottom line is that the data can be edited by N users, but in fact the ideal option is that the one who first opened the record edits it, the rest can open the record only for viewing.

The approach you describe is called pessimistic locking. I propose to search for this term as this is implemented.