WhatBrokeToday
GTA 6FAQ
GitLab

GitLab Backup Procedure Fails Due to PostgreSQL Major Version Mismatch

high

Is it fixed? Not yet.

Ongoing since Nov 18, 22:00 UTC. First reported Nov 18, 22:00 UTC. Not on the vendor’s status page yet.

What happened

GitLab experienced a database backup failure because the backup procedure utilized pg_dump version 9.2 while the database was running PostgreSQL version 9.6. This major version discrepancy caused pg_dump to throw an error and prematurely terminate the backup process.

What caused it?

A difference in major versions between pg_dump (9.2) and the running PostgreSQL database (9.6) caused pg_dump to produce an error and end the backup.

Source: bsky.app

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on Bluesky post

    The backup procedure was using pg_dump 9.2 while the database ran PostgreSQL 9.6; GitLab says a difference in major versions makes pg_dump produce an error and end the backup.

    Source

Evidence

1 report · 1 BlueskyShow
  1. [1]
    Bluesky First report
    The backup procedure was using pg_dump 9.2 while the database ran PostgreSQL 9.6; GitLab says a difference in major versions makes pg_dump produce an error and end the backup.(opens Bluesky post in a new tab)

    The backup procedure was using pg_dump 9.2 while the database ran PostgreSQL 9.6; GitLab says a difference in major versions makes pg_dump produce an error and end the backup. Source: GitLab, 'Postmortem of database outage of January 31', 10 Feb 2017 ¶32

    by failurecase.com 0upvotes 1comments

FAQ

What happened in the GitLab issue?

GitLab experienced a database backup failure because the backup procedure utilized pg_dump version 9.2 while the database was running PostgreSQL version 9.6. This major version discrepancy caused pg_dump to throw an error and prematurely terminate the backup process.

What is affected by the GitLab issue?

GitLab.

When did the GitLab issue start and end?

It started Nov 18, 22:00 UTC and is still ongoing (6 h 53 min so far). This page updates as it develops.

How do I get alerts for GitLab?

Subscribe to the GitLab RSS feed for every new GitLab incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether GitLab is down. GitLab feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.