Hello,

I am working at EclecticIQ and we are curious about graph analysis over 
PostgreSQL. AGE looks promising so I would like to get more details.

1. Performance optimization

Is AGE also looking to add different data structures / indices to improve graph 
query type performance ?

As an example, I can refer to this Stack Overflow post: Improving Postgres 
performance on graph-like queries of multi-level self-joins (comparison to 
Neo4j)<https://stackoverflow.com/questions/52674380/improving-postgres-performance-on-graph-like-queries-of-multi-level-self-joins>

2.  Graph model on pre-existing data

As I understood so far, in order to use AGE syntax, you have to create the 
graph from scratch with AGE functions.

What about an already existing database with data, will it be possible to use 
the tables in place though a kind of mapping ?

I see 2 benefits out of it. It would save the duplication of all the data and 
keep the storage cost low. Also, it would avoid consistency concerns between 
initial tables and the graph ones.

Is it something on the roadmap for the future or is it technologically 
impossible/too complicated ?

Eric

Reply via email to