Issues

New issue

AGE for MS Azure PostgreSQL
#1524 · aked21 opened on Jan 29, 2024
6
Why do you use Apache AGE?
#1705 · markgomer opened on Mar 18, 2024
45
How to handle the param if there're single quotes in it?
#1722 · 0xnoahzhu opened on Apr 5, 2024
25

Label name resolved from adjacent memory under concurrent edge writes: relation "<graph>.<garbage>" does not exist
apache/age#2588 · opened on Oct 2, 2026
A btree index scan on agtype that starts at a >= bound skips the keys equal to it (n.id >= 995 returns 996 to 1000)
apache/age#2587 · opened on Oct 2, 2026
Performance regression in 1.8.0: every Cypher DELETE costs ~1 ms per edge label in the graph
apache/age#2586 · opened on Oct 1, 2026
[Bug] PG15/1.8.0 regression: query with variable-length edge (VLE) traversal failed
apache/age#2583 · opened on Sep 28, 2026
WHERE n.prop IN $param never uses the property's index; the same list written into the query does (100x on 20k vertices)
apache/age#2582 · opened on Sep 26, 2026
post_parse_analyze hook reads pg_extension inside an aborted transaction; the locks leak into the PGPROC and every later backend on it fails with "failed to re-find shared lock object"
apache/age#2580 · opened on Sep 24, 2026
Mark agtype_string_match_starts_with / _ends_with IMMUTABLE (contains already is)
apache/age#2576 · opened on Sep 19, 2026
MATCH (n) without a label pays PostgreSQL table-inheritance planning cost proportional to the total number of vertex labels in the graph
apache/age#2575 · opened on Sep 19, 2026
Docker images ship no extension update scripts: docker/Dockerfile drops the age--*--*.sql that make install produces
apache/age#2570 · opened on Sep 17, 2026
split() treats the delimiter as a regular expression while replace() treats it literally
apache/age#2568 · opened on Sep 7, 2026
manage_GRAPH_global_contexts loads the whole graph per backend, unbounded and label-unfiltered
apache/age#2567 · opened on Sep 7, 2026
Repeating a destructive multi-row AGE query returns extra rows even without rollback
apache/age#2566 · opened on Sep 7, 2026
After a multi-row path CREATE, WITH * CREATE (...) DELETE ... changes cardinality instead of preserving the incoming rows.
apache/age#2565 · opened on Sep 5, 2026
toInteger() silently clamps out-of-range values to INT64_MAX/MIN instead of raising an error
apache/age#2564 · opened on Sep 4, 2026
age_to*list functions crash the server (SIGSEGV) on array-shaped SQL literals
apache/age#2563 · opened on Sep 4, 2026
The ? (exists) operator crashes the server (SIGSEGV) on an agtype-null left operand
apache/age#2562 · opened on Sep 4, 2026
Inline property map {key: value} is estimated with a fixed selectivity, so multi-hop MATCH flips to a full edge scan + Hash/Merge Join when the key is selective
apache/age#2560 · opened on Sep 2, 2026
2
Entity RETURN DISTINCT followed by UNION fails with type with OID ... does not exist
apache/age#2554 · opened on Aug 27, 2026
avg(toFloat(...)) followed by UNION fails with UNION types double precision and agtype cannot be matched
apache/age#2553 · opened on Aug 27, 2026
Multi-row CREATE followed by startNode/endNode reports a nonexistent graphid
apache/age#2552 · opened on Aug 26, 2026
Inefficient MATCH (a)-[:RELATED]->(b) WHERE id(a) IN ...
apache/age#2548 · opened on Aug 24, 2026
r IN relationships(path) fails with unknown type of agtype container 1610612736
apache/age#2542 · opened on Aug 22, 2026
Variable-length path with RETURN * fails with a row/column definition error
apache/age#2540 · opened on Aug 21, 2026
AGE entity-projection alias audit
apache/age#2538 · opened on Aug 21, 2026
Deleting a matched relationship and then executing full-path MERGE causes a PostgreSQL backend segmentation fault
apache/age#2537 · opened on Aug 21, 2026
1

Navigation Menu

Issues

Issues

Label name resolved from adjacent memory under concurrent edge writes: relation "<graph>.<garbage>" does not exist

A btree index scan on agtype that starts at a `>=` bound skips the keys equal to it (`n.id >= 995` returns 996 to 1000)

Performance regression in 1.8.0: every Cypher DELETE costs ~1 ms per edge label in the graph

[Bug] PG15/1.8.0 regression: query with variable-length edge (VLE) traversal failed

`WHERE n.prop IN $param` never uses the property's index; the same list written into the query does (100x on 20k vertices)

post_parse_analyze hook reads pg_extension inside an aborted transaction; the locks leak into the PGPROC and every later backend on it fails with "failed to re-find shared lock object"

Mark agtype_string_match_starts_with / _ends_with IMMUTABLE (contains already is)

MATCH (n) without a label pays PostgreSQL table-inheritance planning cost proportional to the total number of vertex labels in the graph

Docker images ship no extension update scripts: docker/Dockerfile drops the age----.sql that make install produces

split() treats the delimiter as a regular expression while replace() treats it literally

manage_GRAPH_global_contexts loads the whole graph per backend, unbounded and label-unfiltered

Repeating a destructive multi-row AGE query returns extra rows even without rollback

After a multi-row path `CREATE`, `WITH * CREATE (...) DELETE ...` changes cardinality instead of preserving the incoming rows.

toInteger() silently clamps out-of-range values to INT64_MAX/MIN instead of raising an error

age_to*list functions crash the server (SIGSEGV) on array-shaped SQL literals

The ? (exists) operator crashes the server (SIGSEGV) on an agtype-null left operand

Inline property map `{key: value}` is estimated with a fixed selectivity, so multi-hop MATCH flips to a full edge scan + Hash/Merge Join when the key is selective

Entity `RETURN DISTINCT` followed by `UNION` fails with `type with OID ... does not exist`

`avg(toFloat(...))` followed by `UNION` fails with `UNION types double precision and agtype cannot be matched`

Multi-row CREATE followed by startNode/endNode reports a nonexistent graphid

Inefficient MATCH (a)-[:RELATED]->(b) WHERE id(a) IN ...

`r IN relationships(path)` fails with `unknown type of agtype container 1610612736`

Variable-length path with `RETURN *` fails with a row/column definition error

AGE entity-projection alias audit

Deleting a matched relationship and then executing full-path `MERGE` causes a PostgreSQL backend segmentation fault