- Organisation
- Fresha, United Kingdom
- Predecessor
- more than 20 source-described critical or heavily loaded production databases on PostgreSQL 12
- Destination
- the bounded production database fleet upgraded to PostgreSQL 17
- Workload
- PostgreSQL 17
- Stage
- completed
Evidence boundary: The dated customer engineering evidence proves the bounded completed state by 29 September 2025. It does not disclose an exact private cutover day or prove that every Fresha database was part of this batch.
Verified platform change
Fresha's engineering team states that it upgraded more than 20 production databases from PostgreSQL 12 to PostgreSQL 17 without downtime.
Transition
From: more than 20 source-described critical or heavily loaded production databases on PostgreSQL 12
To: the bounded production database fleet upgraded to PostgreSQL 17
Known unknowns
The dated customer engineering evidence proves the bounded completed state by 29 September 2025. It does not disclose an exact private cutover day or prove that every Fresha database was part of this batch.