Hot replicas with Stolon about stolon HOT 6 CLOSED

@kafkapre Probably this should be cleanly documented. Stolon does ha using streaming replication and by default all the stolon standbys are hot standbys. Currently, to access them, you have to discover or know the standbys addresses/ports (for "static" environments) or in future you can use the stolon proxy (to make it easy to connect to standbys under dynamic environments like kubernetes) (see #132).

Or do you mean something different?

from stolon.

@kafkapre Did my previous comment answered your question?

from stolon.

Sorry for late response. Yes, I intended something like that. I like that stolon proxies would have "mapped" all postgres instances (master + slaves) and they woluld manage and loadbalance read requests among them. But it seem that this functionality is not implemented yet. When do you intend to imlement it? Thanks.

from stolon.

@sgotti so that means that in default installation all standbys are in hot standby mode and stolon proxies proxy read requests to them?

from stolon.

Yes, exactly as you wrote. Only it does not have to be set up as default, it is enough to switch to it via e.g. environment property.

from stolon.

As of now the main purpose is to provide ha and communication to the current master via the proxy. Future use of the proxy to also balance readonly connections to standbys is covered in #132.

from stolon.