Maksim Milyutin

IMO the most reasonable way to handle this issue is to check invariant on critical updated parameters on keeper side (compare with corresponding values kept from local control file) before...

Hi, @jinguiy ! Unfortunately there is no other solution here as to revert `max_connection` setting, turn off `automaticRestart` and restart nodes manually keeping the valid order. But now [PostgreSQL community](https://commitfest.postgresql.org/31/2489/)...

Hi @sgotti ! Thanks for your notes. > The unique issue is what happens when the remote options are wrong and we end with a standby that cannot sync or...

Hi @sgotti ! > @t0k4rt you should try to increase the cluster spec parameter called `syncTimeout` (defaults to 30 minutes). Looks likes it's not documented (and it'll probably require a...

Hi @aswinkarthik ! I think the integration of `pg_basebackup` options to cluster config is bad idea because this clutters up config. IMO It's more appropriate to specify in config a...

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

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...

> 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](https://github.com/sorintlab/stolon/issues/739)

@rjuju could you make review of this PR and give some feedback?

> Why do we need to maintain our own array of queryIds? Why can't we just read PgBackendStatus.st_query_id as pg_stat_activity does? The answer is in tracking of queryId for just...