Note that pg_basebackup is single-threaded, and not encrypted. On Fri, Oct 31, 2025 at 10: 26 AM Sam Stearns <sam. stearns@ dat. com> wrote: Thanks very much, Serkan. We'll have a look. On Fri, Oct 31, 2025 at 3: 28 AM Serkan Akdemir <osmosyum@ hotmail. com>
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Note that pg_basebackup is single-threaded, and not encrypted.
I created a script for incremental backup+merge on PostgreSQL 17+ It creates a full backup and later (next run) incremental backups. Incremental backups are merged to full backup with script, so you have always updated full backup. Disclaimer:
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
ZjQcmQRYFpfptBannerEnd
I created a script for incremental backup+merge on PostgreSQL 17+
It creates a full backup and later (next run) incremental backups. Incremental backups are merged to full backup with script, so you have always updated full backup.
We're running version 17.6. Would anyone be able to point me to, or provide, some sample use cases / scripts / usage to deploy a pg_basebackup full + --incremental strategy as a backup solution, please?
This will be used temporarily as we are migrating to RDS soon which is why we're not going with pgBackRest.
Thanks,
Sam
--
Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com
--
Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--
Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com