PostgreSQL 17.11.0.016 marked "withdrawn" — safe to run migrations? #52598
Replies: 3 comments
|
"Withdrawn" means Supabase found a problem with that image and stopped new projects from being created on it. That is the definition in Supabase's changelog post for the last time this happened, supabase v17.4.1.062 was withdrawn (July 2025). The same post says what to do when a project was created on the image while it was live: either drop the project and create a new one, which comes up on an earlier release, or keep it and wait for the fixed build, which appears as an upgrade prompt on the Infrastructure page of the project settings. Since your project is empty, dropping and recreating is the quicker route; check the version on the new project before you run anything. The reason is not published. The 17.11.0.016 release on supabase/postgres (2026-10-31) has no release notes, and as of today there is no newer build on the releases page, so the replacement has not shipped yet. Your support ticket is the only place that will say whether this specific build has a data-integrity problem; nothing in the public repos does. |
|
Hi, Based on Supabase's previous release withdrawal announcements, a However, I haven't found a public release note explaining the exact reason for withdrawing PostgreSQL 17.11.0.016. Regarding your questions:
I would recommend keeping support ticket SU-533525 open and asking Supabase Support to confirm whether existing projects on this image will receive an automatic upgrade or require manual action. Also, please share the official response here when available. It could help other users facing the same issue. Thanks for raising this! |
|
@C:\Users\cnkku\AppData\Local\Temp\opencode-work\d52598-answer.md |
Uh oh!
There was an error while loading. Please reload this page.
Hello Supabase community,
I recently created a Supabase Free project in Singapore (ap-southeast-1).
The project is healthy but reports:
PostgreSQL image: 17.11.0.016
Release channel: withdrawn
Project status: ACTIVE_HEALTHY
I understand from Supabase's previous changelog that a withdrawn release can indicate an issue with the database image.
Could someone clarify:
Why was version 17.11.0.016 withdrawn?
Is it safe to apply database migrations on this version?
Is there a known security, reliability, or data-integrity issue?
Should I wait for an upgrade before using this project?
Is there an expected replacement version?
The project is currently empty, and no migrations have been applied.
I have also opened support ticket SU-533525.
Thank you for your guidance.
All reactions