Error:Extension "pg_graphqL" has no update path from version "1.5.9" to "1.5.11"
Issue: Extension pg_graphql is using version 1.5.9 but version 1.5.11 is available. Using outdated extension versions may expose the database to security vulnerabilities.
But when I run the SQL: ALTER EXTENSION pg_graphql UPDATE TO '1.5.11';
I receive an error: Extension "pg_graphqL" has no update path from version "1.5.9" to "1.5.11"
Can anybody help?
21 Replies
On Supabase hosted extensions are upgraded by upgrading your postgres version in infrastructure.
Can you please explain to me in detail what does it means? Also what do I need to do in my Supabase to get rid of this error?
You can't run SQL to upgrade.
When you upgrade here:
You will get the latest versions of extensions Supabase offers. You can't upgrade them individually. Note the upgrade will now require you to go to postgres 17 (instead of 15 if you are still on that).
I don't have the Upgrade project button. Please see attached
See the message. You need to go to the extensions tab in the database settings and turn that off. The extension is no longer supported.
By turning that extension off, will it disrupt anything in my database and app? I know this may be a stupid question, but I am learning...
Most likely not unless you personally setup some code in a function to use it. Supabase used to use it I think which is why it is on. But it is deprecated now.
Normally upgrading is just a click of the upgrade button, but with the transition from 15 to 17 there is more involved.
I fear we are going to get a number of questions here on these warning messages.
I will disable it and see and pray nothing breaks
Thank you Gary
And then after I do this, then I can simply upgrade my project?
I can confirm the latest postgres version from Supabase does contain the version you are looking for...
Are you in production?
There will be some downtime during the upgrade.
yes, I am in production
How much time?
Depends on size of database.
For my test instances it is usually under 5 minutes.
The warning says 5 minutes to an hour.
Is there a feature you need in 1.5.11?
If not I would wait awhile longer just to give more time for Supabase to settle on 17 changes/upgrades.
Also typically you should have a dev instance you test upgrades out on before you implement them on a live production app.
I don't think so but I need to check the docs.
If I wait as you suggested, I am still left with that security issue
I know that Gary but I am using Lovable for coding and they don't have support Supabase instances yet... I know I will need to switch to Cursor and develop advanced coding skills as my user base grows
But if something breaks, I can always roll back to backup that supabase stores daily so I am safe with this right?
I honestly don't know if going back restores the database version or not. A logical backup probably is just SQL so would not care what DB version is running. Meaning it would stay 17.
Also restoring from backup is still painful as you lose anything going on in the meantime especially with daily backups and will have storage/file data to clean up if you are using that feature.
Understood. So what is your final advice for me in addition to just waiting? What do I do with my security issue?
I notice that 1.5.11 is for security fixes only. But I don't know what they are.
I messages support so will see
messaged
Looks like the version came out 5 months ago...
Did not find any info in my quick search on what the security fix was.
I don't use it so will leave it to you and support.
Cool
Np. Thank you Gary