How we upgraded PostgreSQL at GitLab.com

In May 2020, GitLab.com, in collaboration with OnGres, successfully upgraded its main PostgreSQL cluster from version 9.6 to 11. This upgrade, motivated by the need to discontinue support for PostgreSQL 10.0 and prepare for the end-of-life of version 9.6, involved a meticulously planned process that included automation, regression testing, and comprehensive blueprint and design documentation. The upgrade was executed during a maintenance window and involved transitioning a 12-node cluster handling 6TB of data and up to 300,000 transactions per second. Key improvements in PostgreSQL 11, such as native table partitioning and enhanced query parallelism, were among the driving factors for the upgrade. The project was divided into phases that involved developing and testing automation scripts, integrating with configuration management, end-to-end testing in a staging environment, and finally executing the upgrade in production. A thorough rollback plan was prepared to ensure minimal downtime and maintain data consistency. The entire process was characterized by a commitment to Infrastructure as Code (IaC) and automation, reducing human error and ensuring a seamless transition. The upgrade was documented and recorded, providing valuable insights into the complexities and challenges of such a large-scale operation.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.