That was the moment I understood the need for query-level approval in Pgcli. Not query logging. Not read-only replicas. Real, human review before a dangerous command runs.
Pgcli Query-Level Approval turns a powerful database client into a safe execution environment. It gives you a checkpoint between writing SQL and running it against production. The feature intercepts queries, analyzes them, and waits for an explicit sign-off before sending them to the database. Dropping a table or mass-updating millions of rows no longer happens by accident.
With query-level approval, you still get the speed and autocompletion Pgcli is known for, but you gain a safeguard that reduces risk to near zero for destructive commands. You can tailor approval rules for your team. Require review only for DELETE or ALTER TABLE. Set triggers on queries that affect more than a certain number of rows. Configure approval for specific schemas or databases.