Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 70%
Response Time: 4h
First Timer Success: 63%
zalando/postgres-operator has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zalando/postgres-operator respond to incoming external pull requests in approximately 3.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 65.1 places zalando/postgres-operator in the A tier.
The external contributor pull request merge rate for zalando/postgres-operator is 70.0%, based on public PR activity from non-core contributors.
zalando/postgres-operator currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in zalando/postgres-operator. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/zalando/postgres-operator?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (88% approval). Large PRs (>500 lines) take ~18 hours (32% approval). Keep your diff compact for rapid review.
Type of issue: Feature request Which image of the operator are you using? Not applicable (UI component issue). Describe the problem: The backoff library (litl/backoff) was archived in August 2025 and is no longer maintained. It is also incompatible with Python 3.14+ due to the removal of the deprecated asyncio.iscoroutinefunction() API. The Postgres Operator UI currently depends on backoff==2.2.1 (pinned in ui/requirements.txt) and uses it in ui/operator_ui/main.py: from backoff import expo, on_exception @on_exception(expo, RequestException) def get_target_namespace(): ... Describe the solution: Migrate to backon — a modern, actively maintained evolution of backoff. It is a drop-in replacement: change only the import statement. -from backoff import expo, on_exception +from backon import expo, on_exception -@on_exception(expo, RequestException) +@on_exception(expo, RequestException) The dependency change in ui/requirements.txt: -backoff==2.2.1 +backon>=4.3.0 Why backon? Zero de
Please, answer some short questions which should help us to understand your problem / question better? Which image of the operator are you using? the internally deployed one :) Where do you run it - cloud or metal? Kubernetes or OpenShift? k8s Are you running Postgres Operator in production? yes Type of issue? feature request With one master and three replicas, I want to set different maxDBConnections and mode for the replica connection pooler, similar to the connectionPooler settings, but just dedicated to the replica pooler. Setting the maxDBConnections to what we could use one the replicas, would be too much for the one master.
Please, answer some short questions which should help us to understand your problem / question better? Which image of the operator are you using? master branch Where do you run it - cloud or metal? Kubernetes or OpenShift? Cloud (on-prem K8s) and kind (local) Are you running Postgres Operator in production? yes Type of issue? Bug report Description When a Postgres cluster undergoes an update that requires a rolling update of pods, the operator hits a race condition during the role synchronization phase. It attempts to execute syncRoles(), but because Postgres is still starting up and temporarily in recovery mode, the database is read-only. This causes the sync to fail. postgres-operator/pkg/cluster/cluster.go Lines 1147 to 1151 in 4d40270 c.logger.Debug("syncing roles") if err := c.syncRoles(); err != nil { c
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to zalando/postgres-operator, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of zalando/postgres-operator acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
zalando/postgres-operator has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 65.1 places zalando/postgres-operator in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zalando/postgres-operator currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zalando/postgres-operator are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.