Gabriele Bartolini: CloudNativePG and Crunchy PGO: an honest, opinionated comparison
The article provides a comparison between CloudNativePG and Crunchy PGO, two popular open-source operators for PostgreSQL on Kubernetes. It discusses their architectural differences, backup strategies, and community health. The author, a co-founder of CloudNativePG, acknowledges his bias while highlighting the strengths and weaknesses of both operators.
- ▪CloudNativePG and Crunchy PGO are two widely adopted operators for running PostgreSQL on Kubernetes.
- ▪The article emphasizes the architectural divide between the two operators, particularly in their approach to high availability management.
- ▪Crunchy PGO relies on Patroni for high availability, while CloudNativePG takes a different approach by leveraging the Kubernetes API.
Planet PostgreSQL files mainly under programming. We currently carry 28 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 | Unleashing the Power of Postgres in Kubernetes |
| Canonical URL | https://postgr.es/p/9jm |
| Publication time | Mon, 18 May 2026 06:54:47 +0000 |
| Retrieval time | 2026-05-18T07:04:56.123Z |
| Last seen | 2026-05-18T07:04:56.123Z |
| 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 | 4tIY_IlRsSsV |
| 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
CloudNativePG and Crunchy PGO: an honest, opinionated comparison18 May 2026·16 minsPostgresql Postgres Kubernetes K8s Cloudnativepg Cnpg Dok Data on Kubernetes Crunchy Pgo Operator Comparison High Availability Backup Migration Patroni Security Openssf Governance CNCF Observability Logging Logical ReplicationTable of ContentsCrunchy’s pioneering roleThe architectural divideDirect Pod managementThe Instance ManagerOn Kubernetes API server availabilityImage design, footprint and securityMajor version upgradesBackup and recoveryObservabilityCommunity health and governanceMy honest conclusionThis article compares CloudNativePG and Crunchy PGO, two of the most adopted open-source operators for running PostgreSQL on Kubernetes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Unleashing the Power of Postgres in Kubernetes.
Discussion
0 comments
