PGD Release Cadence · Customer Survey

Your perspective on PGD's release future

We are taking a fresh look at how PGD releases are structured and published, with the goal of giving customers a predictable cadence that aligns with how enterprise organizations actually plan and operate. Your feedback will directly inform how we approach releases, version support windows, and upgrade guidance.

  • Completion Time4–5 minutes
  • ClosesMay 15, 2026
Responses are shared only with the EDB product team.
Before we begin

Why we're asking

PGD is trusted by some of the world's most demanding organizations, and we take that responsibility seriously. As we evolve our release strategy, we want to make sure it reflects the realities of enterprise planning — not just what works for us internally. This short survey helps us understand what you need so we can build a release model that's genuinely easier to plan around. We greatly appreciate your input and feedback.

Question 1 of 9
Proposal 1
Proposal 1
Proposal 2
Proposal 2
Proposal 3
Proposal 3

On the left are three possible approaches to how PGD could be structured going forward. Please rank them in order of preference.

Strongest Preference
  • 1 Proposal 2 — One feature release per year, regular patches. One feature-bearing release on a fixed annual schedule. Patch releases for bug fixes and security updates in between.
    Trade-off: You may wait up to a year for a specific capability outside the patch scope.
  • 2 Proposal 3 — One PGD version per PostgreSQL version. PGD and PostgreSQL release together annually. One coordinated upgrade decision per year.
    Trade-off: A PGD major upgrade requires a PostgreSQL major version upgrade at the same time.
  • 3 Proposal 1 — Multiple feature releases per year. New features ship as ready, several times a year, across multiple supported PostgreSQL versions.
    Trade-off: More upgrade events and higher likelihood of instability between versions.
Least Preference

Thank you for your response.

Your input directly shapes the PGD release roadmap. The product team will review every response as we finalize our approach.

You can close this window.