-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional syncing mechanisms #389
Comments
Hi @sgotti ! Is there anybody who is working on this issue? |
@maksm90 no one that I'm aware of. |
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. |
|
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).
The text was updated successfully, but these errors were encountered: