kysmou commented on issue #64:
URL: https://github.com/apache/incubator-age/issues/64#issuecomment-838151856


   I pulled the latest source down from age-github.
   Tested as instructed by you and confirmed that the explain execution plan 
was shown.
   testdb=# SELECT *
   testdb-# FROM cypher('test_graph', $$
   testdb$# EXPLAIN MATCH p=(a)-[v]->(b)
   testdb$# RETURN p
   testdb$# $$) as (p agtype);
                                               QUERY PLAN                       
                     
   
--------------------------------------------------------------------------------------------------
    Gather  (cost=1000.00..143753.34 rows=35015 width=32)
      Workers Planned: 2
      ->  Nested Loop  (cost=0.00..139251.84 rows=14590 width=32)
            Join Filter: (graphid_to_agtype(v_1.end_id) = 
graphid_to_agtype(b.id))
            ->  Nested Loop  (cost=0.00..19871.84 rows=2430 width=96)
                  Join Filter: (graphid_to_agtype(v_1.start_id) = 
graphid_to_agtype(a.id))
                  ->  Parallel Append  (cost=0.00..17.73 rows=405 width=56)
                        ->  Parallel Seq Scan on "RELTYPE" v_1  
(cost=0.00..15.71 rows=571 width=56)
                        ->  Parallel Seq Scan on _ag_label_edge v  
(cost=0.00..0.00 rows=1 width=56)
                  ->  Append  (cost=0.00..28.00 rows=1201 width=40)
                        ->  Seq Scan on _ag_label_vertex a  (cost=0.00..0.00 
rows=1 width=40)
                        ->  Seq Scan on "Person" a_1  (cost=0.00..22.00 
rows=1200 width=40)
            ->  Append  (cost=0.00..28.00 rows=1201 width=40)
                  ->  Seq Scan on _ag_label_vertex b  (cost=0.00..0.00 rows=1 
width=40)
                  ->  Seq Scan on "Person" b_1  (cost=0.00..22.00 rows=1200 
width=40)
   (15 rows)
   
   Thank you.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to