Re: FDW wrapper for clustered app management - Mailing list pgsql-general

From Albe Laurenz
Subject Re: FDW wrapper for clustered app management
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17D7872C@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to FDW wrapper for clustered app management  (Jerome Wagner <jerome.wagner@laposte.net>)
Responses Re: FDW wrapper for clustered app management  (Jerome Wagner <jerome.wagner@laposte.net>)
List pgsql-general
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
> connections from the database and this way all the servers would become visible with R/W access.
> 
> Is that a sound idea or does it look horrible ? Would it be reasonable to connect in this way to a
> cluster of 1, 10, 100, 1000 or more servers ?
> 
> is there an existing xxxx_fdw wrapper that would look like a good candidate for such a direct access
> inside an application ? Then I would have to implement the protocol corresponding to this xxxx_fdw
> inside my application.

What is the application you want to access this way?

Does "cluster" mean that data is distributed (sharded) across these servers?

Can you reasonably translate SQL access predicates so that you can push down
WHERE conditions to the remote servers?  If not, every access would have to pull
the entire foreign table into the PostgreSQL server before applying the conditions.

Under the right conditions, such a setup could work, e.g. to join data from
different data sources.  How many servers make sense probably depends a lot on how
you want to use them.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: FDW wrapper for clustered app management
Next
From: Jerome Wagner
Date:
Subject: Re: FDW wrapper for clustered app management