stolon icon indicating copy to clipboard operation
stolon copied to clipboard

Additional syncing mechanisms

Open sgotti opened this issue 7 years ago • 5 comments

Currently stolon only sync from primary using pg_basebackup since it's the most safe and easy way to do this.

We could add different syncing mechanisms (i.e. from backup, rsync etc...).

The difficult part of this different mechanisms is to check that the standby contains valid postgres data files (i.e. it was restored from the right backup).

sgotti avatar Dec 18 '17 13:12 sgotti

Hi @sgotti ! Is there anybody who is working on this issue?

maksm90 avatar Oct 12 '18 14:10 maksm90

@maksm90 no one that I'm aware of.

sgotti avatar Oct 12 '18 14:10 sgotti

AFAICS it's necessary to implement an additional option to recover replica from third-party source similar to pitr mode of cluster initialization and enter this node into cluster. And config options have to duplicate the subset of PITRConfig, namely it have to comprise dataRestoreCommand and archiveRecoverySettings options. Right?

maksm90 avatar Oct 12 '18 15:10 maksm90

@maksm90

AFAICS it's necessary to implement an additional option to recover replica from third-party source similar to pitr mode of cluster initialization and enter this node into cluster. And config options have to duplicate the subset of PITRConfig, namely it have to comprise dataRestoreCommand and archiveRecoverySettings options. Right?

This is a different RFE from this one. Currently replicas only sync from the primary. Please open a new RFE issue and/or a PR implementing this.

sgotti avatar Nov 29 '19 15:11 sgotti

This is a different RFE from this one. Currently replicas only sync from the primary. Please open a new RFE issue and/or a PR implementing this.

Done

maksm90 avatar Dec 06 '19 16:12 maksm90