supabase
Enable Orioledb rewind GUCs
Enables the GUCs that power OrioleDB fast rewind
Currently configured for 20 mins max rewind
Tested locally to work
This is to get an early prototype in the hands of interested customers. In the long term we'll get a dedicated API endpoint for it. In the short term it'll be usable by
- hitting
select orioledb_rewind_by_time(1200);via/v1/projects/{ref}/database/query - Restart the database with
/platform/projects/{ref}/restart-services
For 2-7 second rewind times
Since the next Orioledb release we temporarily limited rewind to IS_DEV=1 builds only. This is for the prod users (hosted instances) couldn't shut down their clusters accidentally while trying this feature. So for trying this feature (for self-hosted users) I propose Orioledb should be built with IS_DEV=1. But not add IS_DEV=1 for the AMI for hosted users. @samrose
@pashkinelfe we're moving to make this generally available on the platform so AI builders can start testing/integrating against the behavior prior to the betra
The image is in alpha with free-tier only users who have consented to the risks, so i think we're okay to enable it on the oriole ami
If I misunderstood something and this PR won't be used for hosted OrioleDB AMI (except "special" AMI for AI builders), please LMK @olirice
The intent is for it to be the official OrioleDB image on the platform. Right now I'm just cutting one for staging to make sure everything works. we can coordinate in slack for if/when its safe to make it the default config
@olirice then let's do this PR without IS_DEV=1. It will work with the current release of Orioledb. And let's discuss how that should be in the next (upcoming) release later in slack.
I moved it back into draft until we get through those changes. Currently just want to make sure i can get it passing E2E on staging