PostgreSQL support

PostgreSQL Support for Self-Managed, RDS, Aurora and Kubernetes Operators

Last reviewed by Tyler Eastridge

AceMQ supports PostgreSQL 24/7 across Americas, EMEA and APAC on self-managed servers, Amazon RDS and Aurora, Azure and Google Cloud managed services, and operators such as CloudNativePG. Most calls start with one of three problems: autovacuum that falls behind and approaches transaction ID wraparound, WAL that fills a disk, or a failover that did not behave as designed.

PostgreSQL 14 gets its last community release on 12 November 2026, and PostgreSQL 13 already has. AceMQ runs the upgrade as a project, then supports the new version 24/7: a senior engineer on a live bridge for a P1 (response targets from 15 minutes, by plan), and a written root-cause analysis after each one. Start with an HA review (1 to 4 weeks) before the cutover; PostgreSQL 11 to 14 can be kept patched through OSSeva while you move.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ PostgreSQL consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Seven PostgreSQL problems we are called about most, with the catalog view or setting we look at before changing anything.

Common PostgreSQL production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Autovacuum never catches the hot tableCheck pg_stat_user_tables for n_dead_tup and last_autovacuum, and pg_stat_progress_vacuum. Per-table autovacuum_vacuum_scale_factor set low for the largest tables, and a long-running transaction that holds the horizon back, are the usual fixes.
A replication slot holds WAL and the volume fillsQuery pg_replication_slots for restart_lsn and active. An abandoned logical or physical slot retains WAL forever, and max_slot_wal_keep_size is the safety net.
Connection counts hit the limitCheck pg_stat_activity grouped by state and application. Hundreds of idle sessions mean a pooler (pgbouncer in transaction mode) rather than a larger max_connections, which costs memory per backend.
Plans flip after a statistics changeCompare EXPLAIN (ANALYZE, BUFFERS) before and after, check default_statistics_target and extended statistics on correlated columns, and review pg_stat_statements for the regressed query.
Commits stall on the primaryCheck pg_stat_replication for sync_state and replay lag, wal_sync_method and storage latency. A synchronous standby on a slow link turns every commit into a network round trip.
Checkpoints cause periodic latency spikesCheck pg_stat_bgwriter (or pg_stat_checkpointer on 17 and later) and the checkpoint_timeout and max_wal_size settings against write volume.
Index bloat after bulk deletesMeasure with pgstattuple and rebuild with REINDEX CONCURRENTLY in a window.

P1 closure includes a short report covering the trigger, what we changed and the monitor that would catch it sooner.

Disk filling because of WAL and the primary is close to stopping? Request a quote and a PostgreSQL engineer replies within the hour.

Contact Us

Deployment coverage

Which PostgreSQL deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor or platform coversExcluded
Self-managed community PostgreSQLEverything operational: HA design, backups, tuning, upgrades, security configurationNo single vendor existsDefects needing a change to PostgreSQL's code
Amazon RDS and Aurora PostgreSQLSchema, queries, parameter groups, replication, upgrade planningAWS runs the service and failoverFaults in the AWS service layer
Azure Database for PostgreSQL, Cloud SQL, AlloyDBThe same, within each platform's limitsThe cloud provider runs the platformProvider control-plane faults
Operators (CloudNativePG, Crunchy, Zalando)Operator configuration, failover behaviour, backupsThe operator vendor covers its own subscriptionKubernetes control plane
Tanzu Postgres and distributed PostgreSQL (Citus)Operations and upgradesBroadcom or the Citus vendor for their productsProduct defects

Support options

Who is the vendor for PostgreSQL?

There is none. The PostgreSQL project's own support page says that commercial support is available from many different companies, and lists them by region on request, without endorsing them. So the useful comparison is between kinds of provider.

What it offers
Gap to ask about
CommunityMailing lists, documentation
CommunityNo response time
Cloud providerSupport for the managed service
Cloud providerNot the database design or your queries
Distribution vendorsSupport on their packaged distribution
Distribution vendorsYou may have to run their build
AceMQ independent support24/7, response targets from 15 minutes, by plan, on the PostgreSQL you run, wherever it runs
AceMQ independent supportNo vendor patches; PostgreSQL has none to give

What's Included

Everything in your PostgreSQL support contract

Vacuum, replication, connection handling, backups and upgrades are all inside the agreement, for self-managed servers and the cloud services you run.

  • 01

    Emergency Incident Response

    Database down, disk full, replication broken, or a primary that won't accept writes. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose, not a ticket acknowledgement.

  • 02

    Major Version Upgrade Project

    PostgreSQL 14 is the common starting point. We plan the move to a supported release with pg_upgrade or logical replication, rehearse it on a restored copy of production, check extensions and drivers first, and run the cutover with you. The support contract starts on the new version.

  • 03

    HA Review: The Entry Offer

    A 1 to 4 week review of your Patroni or repmgr setup, failover behaviour, backups and restore drills, and replication lag, done before the upgrade so the cutover has a tested fallback. The written findings become the upgrade plan.

  • 04

    Query, Vacuum & Bloat Tuning

    EXPLAIN (ANALYZE, BUFFERS) on your real workload, extended statistics, per-table autovacuum tuning, and online bloat removal with pg_repack where a rewrite would otherwise need a maintenance window.

  • 05

    CVE & Patch Advisory

    Alerts for CVEs affecting your exact PostgreSQL version and extension set, with tested minor-version upgrade paths. For releases the community has stopped patching, OSSeva supplies patched builds of PostgreSQL 11 to 14 while the upgrade is scheduled.

  • 06

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the configuration, index, or query change that prevents recurrence. Delivered as standard, not on request.

Why AceMQ

Why PostgreSQL teams call us instead of searching forums

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your schema, your replication topology, and your churn profile — so a P1 call starts with a hypothesis rather than an interview about your environment.

  • No First-Line Triage Layer

    You reach a senior PostgreSQL engineer directly by phone, email, or Slack. No help desk collecting details to relay, and no escalation approval between you and someone who can read a plan and act on it.

  • We Fix Vacuum Properly, Once

    Most autovacuum advice on the internet is a global setting change that helps for a month. We tune per-table thresholds against actual dead tuple churn and find the session or slot holding the xmin horizon — because that's the part that keeps coming back.

  • RDS, Aurora, and Self-Managed

    Aurora is not Postgres with better hardware; its storage layer changes checkpoint behaviour, failover semantics, and how replication lag presents. We support all three models and we know where the managed abstractions leak.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am wraparound warning is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Full-Stack, Not Just the Database

    We diagnose across the connection pooler, the ORM's query generation, storage latency, filesystem and kernel settings, and Kubernetes. A surprising number of Postgres incidents are caused two layers above or below it.

PostgreSQL platforms covered

PostgreSQL from 11 to 18, self-managed or on RDS, Aurora, Azure Flexible Server, Cloud SQL and AlloyDB, plus operator-managed clusters on Kubernetes.

  • Self-managed PostgreSQL 11 – 18
  • Amazon RDS for PostgreSQL
  • Amazon Aurora PostgreSQL
  • Azure Database for PostgreSQL Flexible Server
  • Google Cloud SQL & AlloyDB
  • CloudNativePG / Crunchy / Zalando operators
  • VMware Tanzu Postgres
  • Kubernetes & OpenShift
  • Citus & distributed PostgreSQL
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Hybrid cloud

Version coverage

PostgreSQL versions we support

PostgreSQL versions we support
Release lineWhat we do on it
18 and 1724/7 support and new-cluster design
1624/7 support
1524/7 support and upgrade planning
1424/7 support and an upgrade project
13, 12 and 1124/7 support and upgrade projects

Major upgrades run through pg_upgrade with a rehearsal, or logical replication when downtime must be minutes.

In practice

What does PostgreSQL performance tuning cover, and what does it cost?

It covers pg_stat_statements analysis, plan review with EXPLAIN (ANALYZE, BUFFERS), indexing, autovacuum and bloat, memory and checkpoint settings, and connection pooling. It sits inside a support contract or a scoped health check quoted within 1 hour. Support runs from $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

Escalation Path

Your first hour of a PostgreSQL outage

Calls land with an engineer who reads pg_stat_activity and WAL positions fluently, so the first ten minutes go to the database, not to background.

  1. From 15 min (by plan)first responseEmergencyProduction down: the primary will not accept writes, the data volume is full, transaction ID wraparound has begun
  2. 1 hourfirst responseCriticalSerious degradation: connections maxed out, a replica far behind, a replication slot retaining WAL, queries timing out after a plan flip
  3. 4 hoursfirst responseHighAutovacuum falling behind on a hot table, checkpoint latency spikes, synchronous commits stalling on a slow standby
  4. Next Dayfirst responseStandardQuestions on pooler setup, index maintenance, backup and point-in-time recovery design, upgrade sequencing

Plans set the clock: a database that has stopped accepting writes is not queued behind a planning question.

Want the same PostgreSQL engineers every time something breaks? Ask for a quote or send us a message.

Contact Us

Pricing

What does AceMQ PostgreSQL support cost?

PostgreSQL support typically runs $24,000–72,000 a year. The figure moves with the number of clusters and replicas, whether you use Patroni-style failover or a cloud service, how write-heavy the workload is, and the response plan.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and we answer quote requests within 1 hour. A contract that spans several technologies qualifies for a multi-technology discount.

Support In Practice

PostgreSQL recoveries and tuning work

PostgreSQL support work from AceMQ. Each card links to the full write-up: the database estate, what AceMQ diagnosed or changed, and the result.

All use cases

Support options

Four tiers of PostgreSQL support.

AceMQ offers PostgreSQL support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for databases your DBAs run, proactive monitoring that finds bloat, lag and backup gaps first, managed PostgreSQL on your own infrastructure, and fully managed PostgreSQL on AceMQ infrastructure. Current releases are supported 24/7, PostgreSQL 14 can be upgraded as a project with an HA review first, and PostgreSQL 11 to 14 can be kept patched through OSSeva.

  • Tier 1

    PostgreSQL 24/7 Support & Incident Management

    Your team owns the database, we take escalations

    Best for: Teams with in-house DBAs or developers who need a senior PostgreSQL engineer for incidents beyond their experience.

  • Tier 2

    PostgreSQL 24/7 Support with Proactive Monitoring

    Routine reviews of vacuum, replication and backups

    Best for: Teams that would rather catch slot growth, bloat and wraparound age on a schedule than during a page at night.

  • Tier 3

    Managed PostgreSQL on Your Infrastructure

    We operate PostgreSQL on your servers

    Best for: Organizations that keep databases on their own hardware, VMs or Kubernetes and want operations handled by specialists.

  • Tier 4

    Fully Managed PostgreSQL on AceMQ Infrastructure

    AceMQ takes over PostgreSQL operations as a service

    Best for: Teams whose product depends on PostgreSQL but who do not want to hire and retain database operators.

FAQ

PostgreSQL support questions

Still have questions about PostgreSQL? Email an Expert

Who provides enterprise support for PostgreSQL?

Commercial support comes from many companies, as the PostgreSQL project's own page says, and from cloud providers for their services. AceMQ provides independent 24/7 support for self-managed, managed and operator-run PostgreSQL.

What does a PostgreSQL health check include?

Vacuum and bloat state, wraparound age (age(datfrozenxid)), replication slots and lag, top statements from pg_stat_statements, connection pattern, checkpoint behaviour, backup restore time and security settings, with a ranked fix list.

How do you plan a PostgreSQL upgrade without downtime?

Run a health check, rehearse pg_upgrade or set up logical replication to the new version, replay real traffic, test extensions and drivers, then cut over with a rollback path. Logical replication keeps downtime to minutes.

Do I need pgbouncer or a bigger max_connections?

Usually a pooler. Each backend uses memory and context switching, so raising max_connections moves the failure rather than removing it.

Why does my database slow down every week and recover after a restart?

Often bloat, a long-lived transaction holding back vacuum, or a cache problem. We trace it with pg_stat_activity and vacuum progress.

Do you cover backups and point-in-time recovery?

Yes. We design the backup and WAL archiving setup, check that archives are complete, and time a real point-in-time restore so you know how long recovery takes before you need it.

Do you support RDS and Aurora PostgreSQL?

Yes, for everything above the service. AWS runs the service.

How fast do you respond to a PostgreSQL outage?

From 15 minutes on the top plans, at any hour. Take a Sev 1 where an abandoned replication slot has filled the data volume: an engineer joins a bridge, reads pg_replication_slots, frees space safely and drops the slot, then writes up the root cause. P2 is 1 hour, P3 4 hours, P4 next business day.

Can we start with one PostgreSQL engagement before committing?

Yes. A health check, a vacuum and bloat cleanup, an upgrade rehearsal or a backup restore test can each be scoped as a single job. If incidents continue, an annual agreement adds 24/7 response and engineers who already know your schema and replication topology.

How do you price PostgreSQL support?

Contracts generally fall between $24,000 and $72,000 a year (USD). We count clusters and replicas, check which version and platform you run, ask how critical the write path is, and match a response plan to it. Share those and a quote arrives within 1 hour.

Let's talk

Move Off PostgreSQL 14 on Your Schedule, Not the Community's

Send your version and topology. We reply with a quote within 1 hour, and can start with the health check.

A senior PostgreSQL engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a PostgreSQL Architect