Our stream replication slave server got out of sync so we need to base
backup again.
In case of big databases, can we do incremental backups with pg_basebackup?
Is there any alternative?
Here was a proposal: https://wiki.postgresql.org/wiki/Incremental_backup
In case of big databases, can we do incremental backups with pg_basebackup?
pg_basebackup doesn't support incremental backups, though there's been
discussion of adding some kind of support for it, check -hackers if
you're curious.
Is there any alternative?
There's a few different alternativ
On 21-May-20 08:43, Stephen Frost wrote:
* Christopher Pereira (krip...@imatronix.cl) wrote:
[...]
Is there some way to rebuild the standby cluster by doing a differential
backup of the primary cluster directly?
We've contemplated adding support for something like this to pgbackrest,
We've contemplated adding support for something like this to pgbackrest,
since all the pieces are there, but there hasn't been a lot of demand
for it and it kind of goes against the idea of having a proper backup
solution, really.. It'd also create quite a bit of load on the primary
to checksum
On 24-May-20 15:48, Stephen Frost wrote:
That really shouldn't be possible. I'm very curious as to exactly what
happened that resulted in your primary/replica being 'out of sync', as
you say.
Hi Stephen,
Actually this was more a hypothetical question to find a solution in
case some day one
On 26-May-20 10:20, Stephen Frost wrote:
[...]
"out of sync" is a bit of an odd concept, but having a replica fall
behind a long way is certainly something that can happen and may require
a rebuild from a backup (or from a new sync off of the primary in some
other way, as you suggest below). In
Hi,
When pg_rewind is interrupted due to network errors, the cluster gets
corrupted:
Running pg_rewind for a second time returns "pg_rewind: fatal: target
server must be shut down cleanly".
Trying to fix the cluster with "/usr/pgsql-12/bin/postmaster' --single
-F -D '/var/lib/pgsql/12/mydb
