Hello,
I am considering (postgres 9.3+) the idea of opening a R/W access into a
clustered application by creating one fdw server from a central database to
each server a cluster.
That would imply opening a port on each server inside the application,
listening for incoming connections from the
On 10/17/2014 2:35 AM, Jerome Wagner wrote:
Hello,
I am considering (postgres 9.3+) the idea of opening a R/W access into
a clustered application by creating one fdw server from a central
database to each server a cluster.
That would imply opening a port on each server inside the
Jerome Wagner wrote:
I am considering (postgres 9.3+) the idea of opening a R/W access into a
clustered application by
creating one fdw server from a central database to each server a cluster.
That would imply opening a port on each server inside the application,
listening for incoming
Hello John,
Thanks for your answer. I am also considering a publish/subscribe MQ based
solution (and this may be indeed needed for queuing RPCs).
the data I would like to access R/W is more like
- configuration data
- states of different state machines
- cache values for some keys (reading,
Hello Albe,
Thanks for your answer.
The application is an application that is a sort of supervisor of sub
applications, mainly web oriented. It manage access rights, update versions
of web services, launch services, ..
No the data is not sharded across the servers, but each server can have its
Jerome Wagner wrote:
[wants to access an application server farm with FDW]
Clearly, I am trying to see how I could twist the fdw wrappers into a sort of
manhole inside the
application, without resorting to a classic event based mechanism.
That's too metaphorical for me to understand.
I
