samrose
samrose
@wokalski As far as I can see the existing affordances for declarative vs imperative do not support what you describe above.
Next steps are to work on the tests for this upgrade + default settings.
@encima re-ran the failed test.
@Crispy1975 I was going to wait to merge this until you had a chance to test it out in staging. Just wanted to add this as a status on this...
We needed to handle the lib that pg_cron worker uses on start of postgres server cluster. So, we're going to add a file pg_extensions.json and read that, and set the...
> > We needed to handle the lib that pg_cron worker > > @samrose Could you elaborate on that? Which lib does it need and why do we require a...
> > We needed to handle the lib that pg_cron worker > > @samrose Could you elaborate on that? Which lib does it need and why do we require a...
> > However, the AMI and Nix package won't know which version is being restored to. So, when a restore is triggered, the version that was active at backup time...
> THIS pr is for pg_cron. We are packaging and releasing these multiversion one extension at a time. and pg_cron definitely needs this extra handling, due to worker starting at...
all of this multi version work will be solely for physical backup approach fwiw. so, anything we do in multiversion extension pkg will be due to initial testing and confirming...