Enterprise-Grade Support
for Open-Source PostgreSQL

Our PostgreSQL support service covers everything needed to keep your databases reliable, secure, and performant. This includes troubleshooting production issues, performance optimization, query tuning, architecture guidance, upgrades, and operational best practices.

Beyond reactive, Q&A-style support, we also provide strategic guidance for the long-term health and evolution of your PostgreSQL environment. We conduct regular reviews to ensure your database is operating optimally and remains prepared for changes such as traffic growth, new application features, or evolving infrastructure requirements. Our structured approach to database health checks is described in our white paper:

PostgreSQL Maintenance: A Practical Health Check Guide.

We also maintain regular touchpoints with your team to review database performance, architecture, and operational practices. This helps ensure your system design continues to support your business goals, for example, implementing the right architecture for analytics pipelines, replication setups, or change data capture (CDC) workflows. You can see an example of our recommendations for building real-time data pipelines in our white paper:

Seamless Data Propagation and Real-Time Analytics with Apache Flink and PostgreSQL CDC.

In addition, we offer in-depth consulting sessions focused on architectural reviews, system optimization, and scaling strategies.

Working with us also means your internal DBAs and developers gain ongoing knowledge and guidance from experienced PostgreSQL specialists. When helpful, we run seminars, workshops, or Q&A sessions to help your team build deeper expertise and operate PostgreSQL more effectively.

PostgreSQL is an open-source database, which means no single company can directly integrate patches into the main PostgreSQL codebase.

Any proposed change must go through a rigorous community review process. Patches are submitted and discussed through the PostgreSQL development workflow, primarily via CommitFest, where contributors review, test, and refine proposed changes.

Only a small group of trusted contributors called PostgreSQL committers have permission to push changes to the official PostgreSQL Git repository. However, committers do not make unilateral decisions about whether a patch should be included. Instead, they follow the outcome of the community review process.

You can find the full list of PostgreSQL committers here:

https://www.postgresql.org/developer/committers/

Our team has extensive experience working within this process. We have successfully submitted over 400 PostgreSQL bug reports and actively collaborate with the PostgreSQL community. When necessary, we can help prepare and submit high-quality bug reports or patches and guide them through the review process.

More information about the PostgreSQL patch review process can be found here:

https://commitfest.postgresql.org/

Once the support proposal is accepted and the contract is signed, we begin with an onboarding phase to ensure smooth collaboration between our teams.

During this stage, we review your PostgreSQL environment, infrastructure, and operational setup to understand your systems and identify any potential risks. This helps us establish the most effective way to support your team.

We also set up the necessary communication and support channels, which typically include:

• Jira project: A dedicated project where your team can submit support tickets and track ongoing work.

• Chat channel: A shared chat space for administrative coordination and quick technical questions.

• Database access: To provide the most efficient and cost-effective support, access to the database environment is recommended. However, we can also work without direct access if required by your security policies.

There are two main ways to engage with our engineers: Jira tickets or consulting sessions.

Jira support tickets

1. Submit a ticket

   Using your dedicated Jira project, file a ticket describing the issue or request in as much detail as possible.

2. Ticket review

   One of the engineers assigned to your project will review the ticket and contact you if additional information is needed or to discuss the proposed approach.

3. Resolution

   After alignment with your team, the engineer proceeds with the agreed steps to resolve the issue.

4. Follow-up

   Once the issue is resolved, we will notify you and may recommend actions to help prevent the problem from recurring.

For more complex questions, such as architectural discussions, performance analysis, or system design, you can request a consulting session via chat.

Typically the process for requesting consulting sessions works as follows:

• Your team briefly describes the issue or topic in chat.

• We suggest available time slots for a call.

• If needed, we may request preparatory information (logs, metrics, queries, or test results) to better understand the situation in advance.

• During the call, we review the issue together, provide guidance, and agree on next steps.

Depending on the complexity of the topic, we may follow up with additional analysis, another call, or continue working through smaller tasks via chat or Jira tickets.