As a devops / platform guy, I would have typically made something like this by gluing a bunch of cloud / data tools together. e.g. like an ETL tool, orchestrator tool, maybe some process that dumps a DB, run a custom script, etc.<p>After working with extensions more, I really feel like some of these postgres-internal options should be assessed instead of always defaulting to the cloud tools or custom scripting stuff. In a lot of cases, it's way easier and cheaper to just use an extension, and there's really no big risk since it's just using the extension for an ETL job basically.