postgres-xc-developers Mailing List for Postgres-XC

We have an idea to merge GTM Proxy into the XC core and make it an
auxiliary process, like pooler, background writer, logger, etc.
Like any other auxiliary process it would be started with the node, stopped
with the node and serve sessions running under the same postmaster. The
session would be always communicate to GTM via internal proxy.
Configuration parameters specific to GTM proxy will be moved to the main
config file, some of them like GTM host/port are already there, they would
be used by the Proxy, session would be connected to the port where it is
listening, it would be in the same config file.
We see following benefits of doing this:
- We force people to connect to GTM via proxy and achieve better
performance.
- Better maintainability: -1 configuration file, -1 log file, -1 entity to
manage and monitor. The proxy would share main configuration log, main log
file, and postmaster would monitor proxy and restart if it fails, the
housekeeping code is already here.
- Effectiveness: having proxy running under the same postmaster as its
clients would allow to use faster communication channels, like unix
sockets, pipes, shared memory.
- Reliability: if main GTM server goes down GTM proxy able to reconnect to
a promoted standby, but not session. If session would always connect to the
proxy it always would be able to reconnect.
The only drawback we see is that the multiple nodes would not be able to
share the same proxy.
So, any ideas? Is it worth doing? Any pros and cons we are missing?

-- 
Andrei Martsinchyk

StormDB - http://www.stormdb.com
The Database Cloud