Hello,
On 2016-09-15 09:40:44 -0700, Behzad Varaminiyan wrote:
> I am researching Databases for storing and analyzing GIS spatial data.
> PostGIS (and PostgreSQL, of course) seem very suitable for our use cases.
> We also intend to use PostgreSQL functions (Stored Procedures) for custom
> spatial analysis on that data.
> However, we need a database that not only distributes data across multiple
> PostgreSQL instances, but also analyzes data locally in each instance.
> Considering all the above, I concluded that Citus Data must be appropriate
> for us.
Could you expand on what exactly you mean with "analyzing data locally
in each instance"? That computations should be distributed across
multiple nodes, to use more CPU in total / get faster responses? Or
that you want some non-distributed tables?
> What does the community think? Have I made any mistake? Is it feasible?
Citus might be suitable for the use-case. But it depends heavily on what
kind of queries you want to run in a parallel fashion, and what kind of
analytics you're performing. Citus has some restrictions about the kind
of queries it can execute over distributed tables, and those need to
match your application's architecture.
Greetings,
Andres Freund