SHRIDHAR KHANAL: The Right Way to Give a Third-Party DBA Access to Your PostgreSQL Database
July 23, 2026By Shridhar KhanalBlog, Service Security Hardening, Shridhar's Planet PostgreSQL The Right Way to Give a Third-Party DBA Access to Your PostgreSQL Database Giving an external team access to your PostgreSQL database is one of those decisions that deserves a little thought. The easiest option is to hand over a superuser account, but it’s rarely the right one. A better approach is to create a dedicated role with only the privileges they actually need, and it takes just a few minutes to set up.
- ▪July 23, 2026By Shridhar KhanalBlog, Service Security Hardening, Shridhar's Planet PostgreSQL The Right Way to Give a Third-Party DBA Access to Your PostgreSQL Database Giving an external team access to your PostgreSQL database is one of th
- ▪The easiest option is to hand over a superuser account, but it’s rarely the right one.
- ▪A better approach is to create a dedicated role with only the privileges they actually need, and it takes just a few minutes to set up.
Planet PostgreSQL files mainly under programming. We currently carry 28 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 | Stormatics |
| Canonical URL | https://postgr.es/p/9ql |
| Publication time | Thu, 23 Jul 2026 15:55:44 +0000 |
| Retrieval time | 2026-07-26T10:02:19.289Z |
| Last seen | 2026-07-26T10:02:19.289Z |
| 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 | IMBJkjKFrQKw |
| 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
July 23, 2026By Shridhar KhanalBlog, Service Security Hardening, Shridhar's Planet PostgreSQL The Right Way to Give a Third-Party DBA Access to Your PostgreSQL Database Giving an external team access to your PostgreSQL database is one of those decisions that deserves a little thought. The easiest option is to hand over a superuser account, but it’s rarely the right one. A better approach is to create a dedicated role with only the privileges they actually need, and it takes just a few minutes to set up. Over the years, I’ve been on both sides of this conversation. I’ve been the external DBA being onboarded onto a client’s database, and I’ve been the internal engineer deciding what access to grant.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Stormatics.