Jul 26, 2026 · 8 min · 11 segments
In this episode of Scaling Postgres, we discuss migrating to pg\_hardstorage for Postgres backup, PG 19 Beta 2 is released, collecting log stats with pg\_stat\_log and PG 19 checkpoint additions. To…
Creston JamisonHost
Our first piece of content is moving to pgHard storage without changing your recovery strategy.

This is from cyberattack-postgrowskills.com, and they do have migration guides, which I did not read, but it says pgHard storage approaches migration as a gradual operational transition, but that's pretty much what I did because it was logical.

So existing repositories remain in place while new backups are written to a new pghard storage repository.

And he says also historical backups continue to be restored using the tool that created them.

So basically you can eventually retire those processes once the retention timeframes run out.

So yes, right now I am doing double backups, but that's actually something they recommend.

Combined with the dual write migration model, writing to both repositories, your existing one and the new PGA Hard Storage one, teams can evaluate the new environment, validate recovery procedures, and choose a cutover point that fits their own operational schedule.

But with regard to those migration guides, again, which I didn't read, but they do exist, and he has links for them if you're using pgbackrest, want to try another solution, or barman, or wallg.

Again, mine are just scripts using pgbase backup and a way to archive and compress the wall.

Our first piece of content is moving to pgHard storage without changing your recovery strategy.

This is from cyberattack-postgrowskills.com, and they do have migration guides, which I did not read, but it says pgHard storage approaches migration as a gradual operational transition, but that's pretty much what I did because it was logical.

So existing repositories remain in place while new backups are written to a new pghard storage repository.

And he says also historical backups continue to be restored using the tool that created them.

So basically you can eventually retire those processes once the retention timeframes run out.

So yes, right now I am doing double backups, but that's actually something they recommend.

Combined with the dual write migration model, writing to both repositories, your existing one and the new PGA Hard Storage one, teams can evaluate the new environment, validate recovery procedures, and choose a cutover point that fits their own operational schedule.

But with regard to those migration guides, again, which I didn't read, but they do exist, and he has links for them if you're using pgbackrest, want to try another solution, or barman, or wallg.

Again, mine are just scripts using pgbase backup and a way to archive and compress the wall.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.