PostgreSQL CLI Setup
The article discusses the author's PostgreSQL CLI setup for efficient database querying. It highlights the use of various tools like pgcli and pspg to enhance the terminal experience. The author shares insights on configuration for better performance and usability.
- ▪The author prefers PostgreSQL for quick ad-hoc queries against well-defined databases.
- ▪They have created a terminal-based workflow using PostgreSQL service configs, pgcli, and pspg.
- ▪The setup allows for fast startup and pleasant interaction, integrating well with the terminal environment.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Co |
| Canonical URL | https://sandrock.co.za/carl/2026/05/my-postgresql-cli-setup/ |
| Publication time | Wed, 03 Jun 2026 03:15:09 +0000 |
| Retrieval time | 2026-06-03T03:41:54.046Z |
| Last seen | 2026-06-03T03:41:54.046Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | IhKA2iMLsBJq |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
My PostgreSQL CLI setup Written by alchemyst in Uncategorized Motivatation My database of choice is PostgreSQL. I often find myself wanting to do quick ad-hoc queries against a set of well-defined databases. Maybe I just want to know the internal id of a customer from their name, or check on the status of a job. If I’m doing real reporting and producing outputs I will usually spin up PyCharm. It’s got amazing db support, which is the same as you would get from JetBrain’s dedicated database product DataGrip. Great ergonomics, but Pycharm takes a while to get started and frankly the setup of all our dbs is onerous enough that I haven’t registered all of them. I also use pgAdmin, but that’s also tedious to set up “just right”.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Co.
Discussion
0 commentsMore from Co
