I have a daily job that does a --fork-from to create an OLAP database. Since it will be used for analytics, I want the fork to be a larger volume, so I’m also using --volume-size 100
.
However, the new pg app seems to ignore that last flag, and the volume is the same size of the source volume.
Any way around this? I would like to avoid doing fly volumes extend, as that would complicate the logic of my script (I’d have to get the volume ID etc).