You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my graph, the deletion of vertex is extremely slow. So I use EXPLAIN to print its plan. However, the EXPLAIN takes nearly the same time as of the original deletion.
How are you accessing AGE (Command line, driver, etc.)?
PostgreSQL 14, psql, AGE 1.5.0
What data setup do we need to do?
I guess you can reproduce it on any data.
What is the necessary configuration info needed?
What is the command that caused the error?
My SQL is:
explain SELECT *
FROM cypher('ldbc_graph', $$
MATCH (person:Person {id: 111})-[l:LIKES]->(post:Post {id: 222})
DELETE l
$$) AS (res1 agtype);
I pstack it and see it is working on 'end_cypher_delete->check_for_connected_edges'
Expected behavior
There are two major expectation:
The EXPLAIN command on deletion should not use that hook to delete the connected edges.
I have built btree index on (start_id, end_id) to accelerate my MATCH cyphers. I guess it is also possible to delete the connected edges through that index, to make it faster, instead of scanning the full table?
Environment (please complete the following information):
Version: [e.g. 0.4.0]
1.5.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
On my graph, the deletion of vertex is extremely slow. So I use EXPLAIN to print its plan. However, the EXPLAIN takes nearly the same time as of the original deletion.
How are you accessing AGE (Command line, driver, etc.)?
PostgreSQL 14, psql, AGE 1.5.0
What data setup do we need to do?
I guess you can reproduce it on any data.
What is the necessary configuration info needed?
What is the command that caused the error?
My SQL is:
I pstack it and see it is working on 'end_cypher_delete->check_for_connected_edges'
Expected behavior
There are two major expectation:
Environment (please complete the following information):
1.5.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: