How to protect postgres database from bad request?

Question

PostgreSQL

Hello!

A question that does not let you fall asleep: for example, there is a multimillion-dollar database, replication is configured in case the master fails. However, replication will not help if the database administrator mistakenly made an incorrect request (for example, UPDATE without WHERE, well, you never know, the human factor), since all requests to the master also go to the slave and as a result we get a pumpkin from two databases (then, of course, some who will be hanged). How can you protect yourself from this kind of error?

Answer 1

Backups and be sure to review all mutating requests.