Heikki Linnakangas wrote:
> (starting yet another thread to stay focused)
>
> Having mulled through all the recent discussions on synchronous
> replication, ISTM there is pretty wide consensus that having a registry
> of all standbys in the master is a good idea. Even those who don't think
> it's *necessary* for synchronous replication seem to agree that it's
> nevertheless a pretty intuitive way to configure it. And it has some
> benefits even if we never get synchronous replication.
>
> So let's put synchronous replication aside for now, and focus on standby
> registration first. Once we have that, the synchronous replication patch
> will be much smaller and easier to review.
>
> The consensus seems to be use a configuration file called standby.conf.
> Let's use the "ini file format" for now [1].
>
> Aside from synchronous replication, there are three nice things we can
> do with a standby registry:
>
> A) Make monitoring easier. Let's have a system view to show the status
> of all standbys [2].
It would be interesting if we could fire triggers on changes to that
status view. I can see that solving many user management needs.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +