Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
PostgreSQL support

PostgreSQL support
in South Africa.

PostgreSQL is free to download and expensive to neglect. Senior PostgreSQL DBAs run production Postgres without the guesswork, with direct access to the engineer and no service desk.
Founded 2019Randpark Ridge and Stellenbosch24/7 supportSenior DBAs, no service deskVendor neutralListed on postgresql.org professional services
Who this is for

When Postgres becomes production.

PostgreSQL usually arrives quietly, chosen by a development team, and becomes business-critical before anyone is formally responsible for it. This service is for the moment that responsibility needs a senior owner.
  • Teams running PostgreSQL in production, on their own servers or on a managed cloud service, without a dedicated DBA.
  • Organisations moving workloads from Oracle or SQL Server to PostgreSQL and wanting the operations side handled properly.
  • Estates where vacuum, bloat and storage growth have never been measured, and the database keeps getting bigger and slower.
  • IT leaders who want a named senior engineer on call, rather than a ticket queue or a community forum.
What is covered

Production Postgres without the guesswork.

24/7 support and managed DBA

Monitoring, maintenance, patching and on-call support under one predictable monthly fee, from the DBA who knows your databases.
  • Direct access to a named senior PostgreSQL DBA
  • Agreed response commitments, reported against
  • One fixed monthly fee, scope agreed upfront

Vacuum, bloat and storage growth

Autovacuum tuned per table where the workload demands it, bloat measured rather than guessed, and storage growth kept under control.
  • Autovacuum settings per table
  • Bloat measured and reclaimed
  • Growth tracked against real usage

Point-in-time recovery

Base backups plus write-ahead log archiving, with recovery drilled and the recovery time measured, so the objective is a fact rather than a hope.
  • Backups proven by restoring them
  • Recovery time measured, not estimated
  • Retention aligned to the business

Replication and high availability

Streaming replication with tested failover, designed around the two numbers the business agrees first: acceptable downtime and acceptable data loss.
  • Failover exercised deliberately
  • Replica health monitored continuously
  • Recovery objectives agreed before any design

Performance tuning

Query plans, indexing strategy and configuration tuned against the workload that actually runs, rather than left at defaults.
  • Execution plans and slow queries reviewed
  • Indexing strategy against the workload
  • Configuration checked, not defaulted

Upgrades and managed cloud

Major-version upgrades planned before community support runs out, and the same judgement applied on managed cloud services, where server administration is handled but database decisions remain yours.
  • Upgrades planned ahead of end of support
  • Managed services such as AWS RDS supported
  • Migrations from Oracle and SQL Server assessed and rehearsed
How engagement works

Three steps, no service desk.

STEP 01

Start with a health check

An independent assessment of vacuum and bloat, backups and recovery, replication, configuration and version risk, ending in a prioritised list of what to fix first.

STEP 02

Agree the scope and one monthly fee

What we take on and what stays with your team is written down, with response commitments that we report against.

STEP 03

Work with a named senior DBA

You deal directly with the PostgreSQL DBA who knows your estate, around the clock, without a service desk between you and the fix.

Proof

PostgreSQL work we can show.

Client names stay confidential unless a client has agreed otherwise, so our case studies are anonymised. Each one describes a real PostgreSQL engagement and the reasoning behind the decisions.
Common questions

Questions we are usually asked.

  • Do you replace our DBA or work alongside our developers?

    Either. Some clients hand the databases over under a managed DBA agreement; others keep the development team in charge and use us for senior operations cover. The split is agreed upfront and written into the scope.

  • Is support genuinely 24/7?

    Yes. Production support runs around the clock under agreed response commitments, and we report against those commitments.

  • We run PostgreSQL on AWS RDS or another managed service. Do you still add value?

    Yes. A managed service handles the server and the patching; it does not tune your queries, size your instance, manage bloat or decide your recovery objectives. Those database decisions remain yours, and that is the work we do.

  • Which PostgreSQL versions do you support?

    Current community-supported major versions, and older ones while we plan the upgrade. The PostgreSQL community supports each major version for roughly five years, and we plan upgrades before that support ends.

  • Can you help us move from Oracle or SQL Server to PostgreSQL?

    Yes. Migration is assessed per workload: what moves cleanly, what does not, and whether it should move at all. It is tested on the target and rehearsed with a rollback path before cutover.

  • How do we start?

    Most engagements start with a health check or a conversation about the estate. Use the form on this page, email expert@radixtrie.com or call +27 63 692 3703 and you will speak to a senior PostgreSQL DBA.

Talk to us

Talk to a senior PostgreSQL DBA.

Tell us about the environment: how many databases, which versions, self-hosted or managed, what is worrying you. A senior PostgreSQL DBA replies directly, and the first conversation is about understanding your estate.
Prefer email or phone? Write to expert@radixtrie.com or call +27 63 692 3703. Offices in Randpark Ridge, Johannesburg and Stellenbosch.

By submitting this form you agree to our Privacy Policy and consent to being contacted about your enquiry. Conversations stay confidential and focused on your environment.

Further reading

More on PostgreSQL.