[WIP] Major Upgrading of Supabase Postgres

[dragarcia]

Primary Objectives

• Closes Upgrade to postgres 13 #35 Bump to Postgres 13
• Closes Compile postgres with LSE enabled #40 Enable Large System Extensions
• Closes Install supautils in the image instead of in the worker #49 Install supautils as part of internal build
• System enhancements
  • reconfigure fail2ban to prevent postgres password bruteforce #36 Reconfigure fail2ban
• Install popular requested extensions
  • timescaledb
  • Select extensions from RFC: new extensions #45
• Additional AMI "bundles" #46 Setup additional Marketplace images
  • PgBouncer Bundle
  • PostgRest Bundle
    • Install PostgRest
    • Make sure that it is not installed by default
  • Complete Bundle

Secondary/ Resultant Objectives

• Shift away from ANXS/postgresql
  • Inevitable if we want to reap the benefits of LSE on Graviton 2 instances
  • It does however open up the following long-term benefits:
    • Increased granularity in modifying PostgreSQL given that we are now building it from source.
    • Able to immediately upgrade to the most up-to-date versions of Postgres
      • Before, we would need to wait for the above role to ensure that the newest version is available under them.
      • Now, we can upgrade as soon as the newest Postgres version is out
  • Configure building Postgres from source
    • Arm
    • x86
  • Add checks to verify Postgres installation
  • Perform regression testing against other, existing tasks
    • Arm
    • x86
• Ensure existing extensions are supported for Postgres 13
  • Arm
  • x86
• Re-establish versioning policy
  • After much thinking, I've changed my mind and realised that following the versioning policy of PostgreSQL could potentially simplify things.
    • Major would be dictated by Postgres
      • Would therefore only change whenever there is a new major of Postgres (eg. Postgres 13, Postgres 14, etc.)
    • Minor would be dictated by Postgres
      • Would therefore only change whenever there is a new minor of Postgres (eg. Postgres 13.2, Postgres 13.3, etc.)
    • Patch would be dictated by us
      • Would change whenever other updates other than the above are made to the image (eg. new extensions, system enhancements, etc.)
    • With this PR, the next version could potentially be 13.3.0

[heliumbrain]

@dragarcia any specifics I could help out with here? Using your image for most of my Postgres-usage, would love to see a 13 version :) I could help you look in to the compatability of exisiting extension if you'd like

[dragarcia]

Hey @heliumbrain! 👋

I could help you look in to the compatability of exisiting extension if you'd like

I'm finishing up bumping the current versions of the existing extensions and testing them against Postgres 13. Should be pushing up the changes to this branch in the next few days. Would always be great to have another pair of eyes to see if everything is working 😄 .

Just wondering, how are you currently using the Supabase Postgres image? Do you build it yourself with this repository, or do you get it from either the AWS/ DO marketplace?

[heliumbrain]

Cool @dragarcia!

Sounds great. Happy to have a look once that is done.

I'm using the image as-is for a few projects and I'm building my own based on yours for some. Never tried it from one of the marketplaces

[dragarcia]

Alright, great! I'll update you again once I get these changes in so you can build the latest version yourself and try it out.

[dragarcia]

Hi @heliumbrain, this took longer to complete than expected. I'll be merging this into develop now.

If you're still keen on building and trying out the image yourself (while we're in the midst of preparing the images for the AWS and Digital Ocean Marketplaces), you can always do so from the develop branch. Here are the steps to build your own image:

• via AWS
• via Digital Ocean