Essential Strategies

for PostgreSQL
Upgrade Success
PostgreSQL, commonly known as Postgres, is recognized as a top relational
database management system (RDBMS) widely chosen by organizations for
efficient and secure data management. This open source platform is
bolstered by an active community, offering an extensive range of features
and capabilities that revolutionize how data is stored, retrieved, and analyzed.

Yet, PostgreSQL isn’t unchanging. It continually evolves, improves, and adapts

to meet the needs of its users and the latest trends. To ensure your
PostgreSQL-powered applications and systems are performing optimally,
staying current with the newest PostgreSQL releases and following the best
practices for upgrades is crucial.

Essential Strategies for PostgreSQL Upgrade Success is your guidebook for

navigating a PostgreSQL upgrade with confidence and expertise. Whether
you’re an experienced database administrator, developer, or IT professional
tasked with overseeing deployments — or just getting started in PostgreSQL
– it’s crafted to be your companion for understanding the best practices for
PostgreSQL upgrades. Inside, you’ll discover…

What to do before starting an upgrade: We provide a checklist that acts as

a guide to ensure all essential measures and precautions are in place for a
seamless and effective upgrade.

How to optimize performance and minimize downtime: Discover strategies

for tuning and optimizing your PostgreSQL environment and ensuring
uninterrupted access to your data after an upgrade.

Techniques for troubleshooting common challenges: Gain insights into

common pitfalls and challenges during PostgreSQL upgrades and learn how
to resolve them effectively.

Ways to safeguard your data: Understand best practices for data

migration, backup, and recovery, ensuring the safety and consistency of your
data throughout the upgrade process.

…and much more.

PostgreSQL is a powerful database system, and with the proper knowledge

and approach to upgrading, you can fully unlock its potential.

Let’s get started.

2
Why you should upgrade PostgreSQL

As everyone who works with databases knows, data

security is always a top concern. Cyber threats continue to
evolve, and a secure database is your first line of defense
against data breaches and vulnerabilities.

Each PostgreSQL version upgrade typically includes critical

security patches and fixes, making your data safer and
less susceptible to attacks.

In addition to security enhancements, upgrading PostgreSQL is vital

for demonstrating compliance with regulatory requirements
mandated by many industries. Such regulations often require the
use of updated and currently supported software, crucial for
meeting standards such as GDPR or HIPAA for data security and
privacy reasons. Updated versions of PostgreSQL often introduce
advanced compliance features like enhanced auditing capabilities,
stronger backup and recovery solutions, and enhanced data
partitioning to meet requirements across various industries.

Performance is another critical driver behind PostgreSQL upgrades.

As your application grows, so does its demands on the database.
The PostgreSQL community continually enhances database
performance, ensuring your application can efficiently handle
increasing workloads. From query optimization to reduced
downtime during maintenance, the performance gains in new
versions can significantly impact your application’s success.

Furthermore, PostgreSQL introduces advanced features and

enhanced compatibility with various data formats and standards
in each new version, meaning an upgrade can provide access to
innovative capabilities that expand your application’s functionality.
A few examples of such enhancements in recent years include:

• Parallel vacuum feature (introduced in PostgreSQL 13): This

allows the vacuum process to run in parallel on different table
indexes, reducing downtime for maintenance requirements in
large databases.
• The MERGE command (introduced in PostgreSQL 15): The MERGE
command enables the execution of conditional SQL statements
that can include INSERT, UPDATE, and DELETE actions within a
single statement.
• Bidirectional replication (introduced in PostgreSQL 16): This
feature facilitates the replication of data between two tables
originating from different publishers for a major advancement
in data synchronization abilities.

Maintaining an up-to-date PostgreSQL database not only meets

the needs of your development teams but also addresses the
critical demands of stakeholders such as legal and infosec
departments, making it a benefit for all involved.

3
Benefits of following best practices

Upgrading PostgreSQL can be complex, but adhering to best practices is worth the effort. By following the recommended
guidelines, you can unlock several crucial benefits:

Optimized performance: Following best practices ensures you get the most out of your PostgreSQL database. You’ll enjoy
improved query performance, scalability, and resource utilization.

Optimized performance: Following best Risk mitigation: Best practices reduce

practices ensures you get the most out the chances of encountering issues
of your PostgreSQL database. You’ll enjoy during the upgrade, making the process
improved query performance, scalability, smoother and less prone to unexpected
and resource utilization. problems.

Regulatory compliance: Adhering to best Enhanced security and integrity:

practices means staying up to date with Upgrading PostgreSQL guarantees you stay
the latest security patches and features, current with the latest security patches
often a requirement of various regulato- and features, fortifying your data against
ry standards to help companies comply potential threats. In addition, best practices
with laws like GDPR and HIPAA. safeguard your data’s integrity during the
upgrade process, preventing data loss and
corruption.

Risks of neglecting upgrades

Staying current with PostgreSQL upgrades is not just a matter of gaining new features; it’s a critical necessity for main-
taining the health and security of your database systems. Neglecting these upgrades can lead to a host of risks, com-
promising both the performance and security of your PostgreSQL environment. These risks include, but are not limited to,
the following:

Performance issues: As your application evolves, outdated PostgreSQL versions may be unable to handle
increased workloads, leading to performance bottlenecks, slow response times, and customer dissatisfaction.

Security vulnerabilities: Older versions of PostgreSQL are more susceptible to security breaches and
cyberattacks, which could compromise sensitive information.

Missing out on enhancements: Without upgrades, you may miss out on feature enhancements and new
functionalities that can drive innovation in your application.

Incompatibility: As technology evolves, older PostgreSQL versions may become incompatible with new software or
hardware, limiting your application’s adaptability and scalability.

Compliance breaches: Not keeping your PostgreSQL up-to-date can lead to substantial compliance risks, as out-
dated versions may not meet current regulatory standards for laws such as GDPR and HIPAA. This could result in
not only data breaches but legal penalties as well.

It’s clear that staying up to date with PostgreSQL upgrades is not just a best practice; it’s a strategic must for any
database. In the next chapter, we will discuss the importance of assessing your current PostgreSQL environment in
preparation for an upgrade and some ways to choose the target version.

4
Assessing your current PostgreSQL environment

The first step in completing a successful PostgreSQL identify potential vulnerabilities.

upgrade is a comprehensive assessment of your cur-
rent deployment to identify anything that could affect Document database configurations
the process. This preliminary evaluation helps to ensure Document the current configuration settings of your
compatibility and prevent potential conflicts with new PostgreSQL database, including parameters related to
PostgreSQL features or changes and allows for creat- performance tuning, connection limits, and resource
ing a tailored backup and recovery plan to safeguard allocation. A detailed configuration record streamlines
your data against any unforeseen issues during the the transition process and aids in replicating settings in
upgrade. We will cover these in more detail a little later, the upgraded environment.
but here are the generalities around assessing your
Identify customizations and extensions
PostgreSQL environment.
Take stock of any customizations or extensions imple-
Determine the PostgreSQL version mented in your current PostgreSQL deployment. These
Begin by identifying the exact version of PostgreSQL could include custom functions, stored procedures, or
running in your environment. This information is crucial third-party extensions. Ensure these components are
for determining compatibility with your applications compatible with the target PostgreSQL version or plan
and tools, planning for what upgrades or patches are for necessary adjustments.
necessary to meet your needs, and ensuring you will be
Backup and disaster recovery assessment
able to fully leverage specific features and improve-
Verify the effectiveness of your existing backup and
ments in the new version to improve your database’s
disaster recovery mechanisms. Confirm that routine
efficiency and performance. It also serves as the base-
backups are performed and test the restoration pro-
line for evaluating the benefits and changes introduced
cess to guarantee data recoverability.
in newer versions.

Evaluate hardware specifications

Examine the hardware infrastructure supporting your
PostgreSQL deployment. Assess key parameters such
as CPU, RAM, storage, and network configurations. Un-
derstanding your hardware provides insights into the
database’s current performance and scalability and
helps you plan for any future hardware needs.

Review system performance

Utilize performance monitoring tools like Percona
Monitoring and Management to assess the overall
health and performance of your PostgreSQL database.
Analyze metrics related to query execution times, re-
source utilization, and system response to get a holistic
view of how well your database handles the existing
workload and where optimizations may be required.

Check version compatibility with applications

Consider the compatibility of your PostgreSQL version
with the applications and tools interacting with the
database. Ensure that any planned version upgrades
align with the requirements of your application stack to
prevent potential compatibility issues post-upgrade.

Review security measures

Evaluate the current security measures, including au-
thentication methods, access controls, and encryption
protocols. Assess the compliance of your PostgreSQL
deployment with security best practices and industry
standards and identify areas for strengthening security
to safeguard sensitive data. In addition, it may be worth
considering having an external security audit done.
These audits provide an unbiased assessment of your
database’s security configurations and can help
Understanding PostgreSQL versions
and release cycles
PostgreSQL introduces a new major version annually, supported for five years post-release. Minor releases, which address
bugs and security fixes, occur at least quarterly or as needed. Major versions can alter the internal format of system
tables and data files, requiring a dump/reload or the pg_upgrade tool for upgrading (more on that later). Minor version
upgrades typically don’t require a database dump and restore, but reviewing the release notes for any change is always
advised.

Each major version release brings enhancements and changes that can impact the upgrade process, so
understanding the differences between versions is crucial. Starting with PostgreSQL 10, major versions are indicated
by a change in the first part of the version number, while minor releases update the last part. For example, an upgrade
from 12 to 12.17 is minor, but moving from 12 to 13 is a major upgrade. Upgrading to the latest available minor release is
recommended to ensure stability, security, and compliance, while major upgrades may introduce complex changes
without backward compatibility for stored data, hence the necessity for a thorough assessment before proceeding.

Choosing a target PostgreSQL version

Choosing the right PostgreSQL version for your requirements entails a comprehensive approach. Review the release
notes for the support lifespan of the version you’re considering; selecting one early in its five-year support cycle can offer
extended stability. It’s also important to compare the features and enhancements of recent versions with your present
and anticipated needs, mainly focusing on aspects that could boost performance or strengthen security.

When choosing a new version, it’s essential to understand which features were added to each release. For instance,
version 16 introduced the JSONlog logging format and pg_stat_io, which provides I/O metrics views, whereas these
features weren’t available in the previous versions. Features like B-tree deduplication and bottom-up index deletion were
added to enhance indexing efficiency starting with version 13, while support for ENUM data type, advisory locks, and
custom background workers has been consistent from version 9.5 onwards.

It’s beneficial to assess the compatibility of the new version with your existing systems and applications as well, so review
the release notes of potential target versions if you’re jumping over multiple releases to understand the changes and the
impact they may have on your environment.

6
Pre-upgrade checklist

Upgrading your PostgreSQL database to a newer version can bring significant benefits, but it’s not a process to be taken
lightly. Even seasoned developers and DBAs can find it daunting, as there is little room for error. Thorough planning and
preparation are essential and help you to:

• Understand the changes between your current version and the one you’re upgrading to and how these changes
might affect your applications.

• Safeguard your data’s integrity by identifying and mitigating potential issues before the upgrade.

• Minimize downtime and reduce the impact on your users.

Here, we’ve outlined a general checklist to serve as a 6. Have a backup and recovery strategy: Before you
roadmap to ensure the necessary precautions and start an upgrade, be sure to take a full backup of
steps are taken for a successful upgrade. your current database, including all configuration
files, tables, triggers, views, and stored procedures.
1. Review the release notes: Read the release notes Once backed up, verify that it can be restored
for the new PostgreSQL version to understand successfully, and test the restored version in a
the changes and improvements made. Look for staging environment to ensure it works properly. In
any deprecated features that could affect your addition, have a clear and tested rollback plan in
databases or applications. case you need to revert to the previous version if the
upgrade fails.
2. Determine your requirements: Assess the demands
of your applications, database workload, and 7. Document and communicate: Inform stakeholders,
performance goals to ensure that the new version including users and management, about the
aligns with your operational needs. upgrade schedule and potential for downtime.
Update your system documentation to reflect any
3. Check compatibility and requirements: Investigate modifications or custom settings in your environ-
whether your system requirements (CPU, memory, ment post-upgrade, and educate your team about
storage, etc.) meet the minimum system require- new features and changes in the PostgreSQL version
ments for the target PostgreSQL version. Check if to which you are upgrading, noting any issues you
your applications, libraries, extensions, customiza- encountered along the way.
tions, and third-party tools are compatible with the
new version. Review the PostgreSQL change log to 8. Set up monitoring and alerts: Implement monitor-
understand the compatibility between your current ing and alerting systems to track your upgrade’s
and target versions, and run pg_upgrade checks to progress and identify any issues.
identify potential incompatibilities with tables and
data types. PostgreSQL recommends that all users 9. Test the upgrade: Set up a testing environment that
run the latest available minor release for whatever mirrors your production environment as closely as
major version is in use, so keep that in mind. possible to test the upgrade process and function-
ality applications.
4. Verify current database health: Check that
there are no active long-running transactions or By incorporating these items into your pre-upgrade
connections that might be affected by the upgrade. checklist, you can ensure that your PostgreSQL upgrade
Use tools like pg_chec` to verify the integrity of the is performed with due diligence, paving the way for a
current database. smoother transition to a new version.

5. Plan for downtime: Schedule a maintenance

window during off-peak hours to reduce the impact
of any downtime. Inform all stakeholders about
the scheduled downtime, and keep in mind that
the larger the database, the longer it may take to
upgrade. Be sure to include some extra time in case
anything goes awry.

7
Methods for upgrading

PostgreSQL upgrades can seem intimidating, but various

tools can help. Tools like pg_upgrade make the transition
efficient by enabling in-place upgrades without necessi-
tating a full dump and reload of the database. For more
comprehensive backups, pg_dumpall is your go-to, en-
suring you have a complete database snapshot before
moving forward. The command-line utility pg_restore is
used to restore a PostgreSQL database from an archive
file, and leveraging Replication can minimize downtime
by allowing you to switch to a standby server during the
upgrade. Here, we’ll cover some basics of each.

pg_upgrade pg_dumpall

The tool pg_upgrade streamlines the PostgreSQL This utility creates a complete backup of all the
upgrade process, enabling an in-place upgrade databases within a PostgreSQL cluster, which is
from one PostgreSQL version to another, allowing particularly valuable when creating a full snapshot
you to avoid the time-consuming task of dumping before an upgrade. It backs up the data and all the
and reloading the entire database—a process that associated global objects like roles and
can be particularly onerous for large databases. tablespaces, which can be crucial for restoration.
This utility works by updating the system catalogs to Using pg_dumpall is a way to safeguard against any
the newer version while preserving the actual data data loss during the upgrade process, as it allows
files, which saves a significant amount of time and you to restore your databases to their exact state
reduces the risk of data transfer errors. It makes for before the upgrade if needed. You may also hear
a swift transition to the latest version of PostgreSQL about pg_dump, which enables you to back up an
with minimal downtime, making it a preferred option entire database or just a selection of database
for mission-critical databases where availability is a objects. For upgrading an entire database,
prime concern. pg_dumpall is the preferred method.

Replication pg_restore

Replication refers to copying and maintaining pg_restore is a tool used to revert a PostgreSQL
database objects across multiple servers, allowing database to its previous state from a backup file
for redundancy and high availability. By setting up made by pg_dump, provided the backup is not in
a standby server that replicates the data from the plain text. This utility executes the required steps to
primary server in real time, you can perform the rebuild the database as it was when backed up.
upgrade on the standby server without affecting the Additionally, the backup files grant pg_restore the
primary. Once the upgrade is successfully flexibility to choose specific elements to restore or
completed and thoroughly tested on the standby, rearrange the restoration sequence.
a failover can be initiated. This makes the upgrad-
ed standby the new primary server, minimizing the
downtime experienced by end-users. This method
ensures that the primary database remains online
during the upgrade, providing continuous service
until the switch is made.

8
Tips for avoiding downtime

In addition to some of the items in the checklist we reviewed

earlier (thorough planning, testing, communication,
monitoring, etc.) and the advantages of tools like
pg_upgrade, there are a few other tips to keep in mind to
minimize downtime when upgrading PostgreSQL:

Implement connection pooling: Connection pooling

solutions like PgBouncer can help maintain database
connections during the upgrade, ensuring applications
can connect without interruption, even when the
database version changes.

Use high availability (HA) clusters: If you have an HA setup

with tools like Patroni, you can perform the upgrade on a
standby node while the primary node continues to handle
traffic. Once the upgrade is successful, promote the standby
to the primary role.

Upgrade extensions and dependencies first: Upgrade

PostgreSQL extensions and dependencies before upgrading
the core database to ensure they are compatible with the
new version.

Utilize rolling upgrades: Consider using this feature for

versions that support rolling upgrades. It allows you to
upgrade one node at a time in a PostgreSQL cluster, r
educing downtime significantly.

Perform test runs: Conduct dry runs in a staging

environment to simulate the upgrade process, identify
potential issues, and fine-tune your upgrade plan.

Engage PostgreSQL experts: If you need clarification on any

aspect of the upgrade process, consider seeking assistance
from PostgreSQL experts like Percona. Our expertise can be
invaluable in ensuring a successful upgrade.

By following these tips and the checklist, you can

significantly reduce downtime and ensure a seamless
transition to the latest version of PostgreSQL while
maintaining the availability of your critical applications.

9
Post-upgrade testing

After upgrading PostgreSQL, conducting comprehensive

post-upgrade testing is crucial to ensure the new system
operates as expected. Here is a checklist of tests and
validations you should perform:

• Check the PostgreSQL version with the `SELECT version();`

SQL command to ensure the upgrade was applied
correctly.

• Verify that every database function operates as it should,

ensuring that triggers, stored procedures, and custom
functions work as intended with the updated version.

• Compare the upgraded database’s performance

against that of the earlier version. Monitor for any
deterioration in system efficiency, query execution
rates, or response times.

• Verify that all data has been migrated correctly and is

intact. This step should include checking for corrupted
data, verifying record counts, and confirming that the
relationships between tables have been maintained.

• Verify that user permissions, access controls, and

auditing features comply with your security rules and
that all security measures operate as intended.

• Test whether the updated database is compatible with

the connected applications. Verify that these applica-
tions can effectively read and write to the database
without encountering integration problems.

• Run a trial backup and recovery procedure with the most

recent PostgreSQL version to ensure these work properly.

• Look through the system logs for any faults or warnings

that may have occurred during the upgrade, which may
help in the early diagnosis of potential issues.

• Run your database through a high-load scenario to

evaluate its resilience and performance to identify
potential bottlenecks or issues related to scalability.

• After completing all tests and ensuring system stability,

finalize the upgrade process by revising any relevant
documentation and notifying stakeholders.

10
Navigating common PostgreSQL upgrade challenges

Upgrading a PostgreSQL database is essential for organizations aiming to enhance performance, strengthen security,
and gain access to the latest features, but the upgrade process is challenging. Here, we’ll look at some of these common
hurdles and offer strategies for overcoming them.

Downtime management
Upgrading often requires downtime, which can disrupt business operations. To mitigate this, admins can plan the
upgrade during off-peak hours or use replication techniques to maintain a standby database, allowing for a switchover
with minimal downtime.

Compatibility concerns
New PostgreSQL versions might not be fully compatible with your existing applications. It’s essential to understand the
modifications in each release, and reviewing the PostgreSQL release notes is a vital step in this process. Upgraded
PostgreSQL versions should be tested in a staging environment to identify and resolve any compatibility issues before
going live.

Performance issues
PostgreSQL upgrades, while beneficial for accessing new features and improvements, can have a significant impact —
for better or worse — on database performance. It’s crucial to conduct a detailed performance analysis after an upgrade
to ensure that the new version either meets or surpasses the performance levels of the previous version. Key steps in this
process include, but are not limited to:

• Benchmarking pre-upgrade performance: Record baseline metrics like query response times, throughput, and
resource utilization (CPU, memory, disk I/O).

• Monitoring performance post-upgrade: After the upgrade, monitor these same metrics to identify any performance
deviations.

• Analyzing query performance: Make sure queries are optimized for the new version, using tools like PostgreSQL’s
`EXPLAIN` for analysis.

• Testing workloads: Simulate real-world scenarios to test the upgraded database under various load conditions.

11
Upgrade methodologies

You must decide between an in-place upgrade using tools like pg_upgrade and a dump-and-restore method. In-place
upgrades are faster but riskier, with fewer rollback possibilities. On the other hand, while more time-consuming, the
dump-and-restore approach offers a safer option with a clearer rollback path if needed.

Resource constraints

Resource limitations can significantly impact the upgrade process. Key issues can include hardware constraints, as
upgrades often require more storage for data migration and backup, as well as increased processing power to handle
new features and the migration process. Network bandwidth is another crucial resource, particularly for large or
distributed databases, as limited bandwidth can slow down data transfer, extending the upgrade duration and
heightening the risk of data inconsistencies or loss during migration.

On top of that, time constraints can present another challenge, especially if upgrades need to be conducted within
limited timeframes to minimize operational disruptions, leading to potentially risky decisions.

Staff training and skill upgrades

Updated versions of PostgreSQL often come with new features or changed functionalities, so you must ensure your
database management team knows them to handle the updated database environment.

Database experts of all levels can encounter issues when upgrading PostgreSQL. However, by planning how to address
compatibility concerns, choosing a migration approach, and monitoring performance, you can minimize the challenges
you face during your upgrade.

12
Optimizing your upgraded PostgreSQL

So, you’ve successfully upgraded your PostgreSQL database. Congratulations… but don’t celebrate just yet! It’s time to
ensure your new version is optimized for performance and stability. Next, we’ll walk you through tuning, monitoring,
maintaining, and documenting your upgraded PostgreSQL database and preparing for backup and disaster recovery.

Performance tuning strategies

Configuration tuning: Each new version of PostgreSQL introduces new configuration options and enhancements. Tools
like PgTune can provide a solid foundation for initial configuration settings, and after upgrading, fine-tuning these
configurations is key, as new versions might add or deprecate specific parameters.

Index optimization: Improving index efficiency can significantly enhance performance, so after the upgrade, consider
using the REINDEX command to rebuild indexes and ANALYZE to update query planner statistics. You should also review
any new indexing features that may have been introduced in the latest version, as they can offer further performance
benefits.

Partitioning and parallel processing: Take advantage of any parallel processing capabilities and partitioning techniques
introduced in the upgraded version of PostgreSQL. These features can improve overall database performance and
efficiency, especially when managing large tables and complicated queries.

Ongoing monitoring and maintenance

Effective ongoing monitoring and maintenance keep your PostgreSQL database performing optimally and help
preemptively identify and resolve potential issues, ensuring the stability and reliability of your database environment.
Here are a few critical steps in this process:

Regular monitoring: Continuously track performance metrics such as query response times and resource usage. Use a
tool, such as Percona Monitoring and Management, that monitors and provides actionable performance data for
PostgreSQL. It captures metrics and data such as Connections, Active Connections, Tuples, and Tuple Activity.

Database health checks: Regular health checks are vital to maintaining a PostgreSQL database’s efficiency and
longevity. Key areas to focus on include database bloat (tables and indexes that have grown inefficiently large), routine
vacuuming of tables (reclaiming storage occupied by “dead tuples,” the old versions of rows), and checking the integrity
and recoverability of backups.

Security audits: Keep database security up-to-date and apply necessary patches as they are released.

Training and knowledge updates: Keep your team’s skills up-to-date with the latest PostgreSQL features and best
practices, which helps in effectively managing and optimizing the database.

Future capacity planning: Take a proactive approach to meet the future demands of your database system. Effective
capacity planning requires a deep understanding of your database’s growth patterns and expected requirements. Be
sure to analyze data volume increases, query load, and transaction rates over time, and monitor how your upgraded
database uses current hardware resources, including CPU, memory, disk I/O, and network bandwidth. In addition, stay
informed about upcoming features and changes in PostgreSQL that might affect resource utilization in your environment.

13
Updating documentation

You will want to document all changes made during and after the upgrade process, including any adjustments in
configuration settings, index modifications, and query optimizations, so that your IT team is aware of the state of the
current database environment.

Thorough and up-to-date documentation also aids in knowledge transfer, especially when onboarding new team
members, and ensures all have access to the latest information.

Establish a new backup and disaster recovery plan

You may have already had a plan in place for the old version of your database, but does it seamlessly transfer over
to the upgraded version? Develop a comprehensive disaster recovery plan for your new PostgreSQL environment that
includes procedures for restoring from backups and failover mechanisms. Be sure to test this plan regularly to ensure its
effectiveness.

Join a PostgreSQL community

Know that you don’t have to take your PostgreSQL journey alone. There are many user groups and PostgreSQL forums
where you can participate in online discussions, ask questions, get answers, and learn about meetups where you can
share your experiences and learn some new tips and tricks.

14
Upgrades are an opportunity for improvement
rather than a task to postpone
Initiating a PostgreSQL upgrade is a complex but crucial task for improving
database performance, security, and scalability. If you find yourself needing
assistance with your upgrade, Percona is here to help.

Our expertise in PostgreSQL covers the entire upgrade journey, from initial
assessment to post-upgrade fine-tuning. With a reliable partner to guide
you through potential challenges, your PostgreSQL upgrade can be executed
smoothly while minimizing downtime and maximizing the benefits of the
new version’s features and enhancements.

For a no-obligation assessment of your PostgreSQL upgrade, reach out to

us today.

Get in touch with Percona

15
percona.com