psql
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
0warn against
Nov 11, 2025first mention
Jun 5, 2026latest mention
Why people recommend it
“I find this to put my psql in a better place as a daily driver.”
“`psql` to probe Postgres databases.”
ML work with agentson “MCP is dead. Long live the CLI”
Show 1 more
“You can use "psql" to dump subsets of data from tables”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Who recommends it in their own words
Threads where it came up
- databow: a Rust CLI to query any database with an ADBC driver 1 mention
- The way CTRL-C in Postgres CLI cancels queries is incredibly hack-y 1 mention
- MCP is dead. Long live the CLI 1 mention
- Instant database clones with PostgreSQL 18 1 mention
- Go ahead, self-host Postgres 1 mention
- Select 1 Touches 5,583 Lines of Postgres Source Code 1 mention
Data: psql.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 6
“I find this to put my psql in a better place as a daily driver.”
> This doesn't really have anything to do with async signal safety. TLS not being async signal safe is explicitly called out on the article as the reason the token is sent in clear text. > Handle it as a synchronous event in a main loop Of course of you rearchitect the client there are better solutions. But again, the article mentions that's not planned for now. By comparison, delegating cancellation to a background
“`psql` to probe Postgres databases.”
“You can use "psql" to dump subsets of data from tables”
“plain psql for analyzing specific queries”
That should be trivial to change: https://github.com/postgres/postgres/blob/d2f24df19b7a42a0944a6926a0ca54168dcefe3a/src/bin/psql/command.c#L4471-L4483