Supabase with PostgreSQL 16

[dbi1]

Hello,

Thinking of using PostgreSQL 16 with Supabase. Does anybody know if there are issues in going with v16 rather than v15?

Thank you.

[AntonOfTheWoods]

So no one has tried? Or this is documented in a super obvious place maybe? Google didn't turn anything up with my search terms...

[AntonOfTheWoods]

One of the core extensions hasn't been modified to work with 16 yet (supabase/supautils#78, if memory serves). I tested at least updating to 15.6 by simply changing the Dockerfile to

...
ARG postgresql_release=${postgresql_major}.6
...

And that seems to work flawlessly. I have no idea why they wouldn't be interested in at least updating to the latest, secure version of 15 but I am maybe missing something...

[kuncevic]

I am looking forward trying it with v16 tho, is it the right docker compose to modify https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml ?

update: just looked into this https://discord.com/channels/839993398554656828/1224702986865999902/1224702986865999902, I suppose they must announce when v16 is officially supported, right?

[AntonOfTheWoods]

PG17 has now been released and still no word on 16, though supautils now claims to support 16, in spite of the above ticket not being resolved. I guess none of their customers have been requesting it!

[PylotLight]

PG17 has now been released and still no word on 16, though supautils now claims to support 16, in spite of the above ticket not being resolved. I guess none of their customers have been requesting it!

Time to try a separate v17 alpine instance with sb to see if it works?

[AntonOfTheWoods]

Ok, so looks like at least this may be moving more quickly this time. https://github.com/supabase/supautils/commits/sam/pg17/ seems to be upgrading supautils to 17, which means we may get 17 support at the same time 16 is available, and that might be sooner rather than later!

EDIT: and maybe even full support here! https://github.com/supabase/postgres/tree/sam/postgres-17-0