dev  

Messages by Thread

• [I] age_to*list functions crash the server (SIGSEGV) on array-shaped SQL literals [age] via GitHub
• [I] toInteger() silently clamps out-of-range values to INT64_MAX/MIN instead of raising an error [age] via GitHub
• [I] The ? (exists) operator crashes the server (SIGSEGV) on an agtype-null left operand [age] via GitHub
• [I] Multi-hop query plans flip to full edge scans + Merge Join when an attribute index on the start vertex exists [age] via GitHub
  • Re: [I] 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 [age] via GitHub
• [I] Missing Docker Hub image for PostgreSQL 17 / AGE 1.7.0 [age] via GitHub
  • Re: [I] Missing Docker Hub image for PostgreSQL 17 / AGE 1.7.0 [age] via GitHub
  • Re: [I] Missing Docker Hub image for PostgreSQL 17 / AGE 1.7.0 [age] via GitHub
  • Re: [I] Missing Docker Hub image for PostgreSQL 17 / AGE 1.7.0 [age] via GitHub
  • Re: [I] Missing Docker Hub image for PostgreSQL 17 / AGE 1.7.0 [age] via GitHub
• [I] Entity `RETURN DISTINCT` followed by `UNION` fails with `type with OID ... does not exist` [age] via GitHub
• [I] numeric aggregate followed by `UNION` rejects `double precision` and `agtype` [age] via GitHub
• [I] Multi-row CREATE followed by startNode/endNode reports a nonexistent graphid [age] via GitHub
• [I] stale TID` after deleting a path-bound vertex [age] via GitHub
  • Re: [I] stale TID` after deleting a path-bound vertex [age] via GitHub
• [I] Inefficient MATCH (a)-[:RELATED]->(b) WHERE id(a) IN ... [age] via GitHub
• [I] `r IN relationships(path)` fails with `unknown type of agtype container 1610612736` [age] via GitHub
• [I] Variable-length path with `RETURN *` fails with a row/column definition error [age] via GitHub
• [I] Variable-length path fan-out followed by `DETACH DELETE` fails with an internal missing-vertex error [age] via GitHub
  • Re: [I] Variable-length path fan-out followed by `DETACH DELETE` fails with an internal missing-vertex error [age] via GitHub
  • Re: [I] Variable-length path fan-out followed by `DETACH DELETE` fails with an internal missing-vertex error [age] via GitHub
  • Re: [I] Variable-length path fan-out followed by `DETACH DELETE` fails with an internal missing-vertex error [age] via GitHub
• [I] AGE entity-projection alias audit [age] via GitHub
• [I] Deleting a matched relationship and then executing full-path `MERGE` causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] Deleting a matched relationship and then executing full-path `MERGE` causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] Full-path `MERGE` followed by a `WITH` constant `STARTS WITH` predicate causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] Full-path `MERGE` followed by a `WITH` constant `STARTS WITH` predicate causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] `CREATE` followed by a `WITH` constant `CONTAINS` predicate causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] `CREATE` followed by a `WITH` constant `CONTAINS` predicate causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] Empty `UNWIND` followed by `MERGE` and a null-filtered `WITH` causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] Empty `UNWIND` followed by `MERGE` and a null-filtered `WITH` causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] Multi-row `CREATE` followed by full-path `MERGE` causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] Multi-row `CREATE` followed by full-path `MERGE` causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] CREATE` followed by a bound-node path read causes a PostgreSQL backend segmentation fault [age] via GitHub
  • Re: [I] CREATE` followed by a bound-node path read causes a PostgreSQL backend segmentation fault [age] via GitHub
• [I] Full-path `MERGE` fails with a path-shape error when two input rows match [age] via GitHub
  • Re: [I] Full-path `MERGE` fails with a path-shape error when two input rows match [age] via GitHub
• [I] Multi-row `CREATE` followed by a second `CREATE` reports `vertex assigned to variable n0 was deleted` [age] via GitHub
  • Re: [I] Multi-row `CREATE` followed by a second `CREATE` reports `vertex assigned to variable n0 was deleted` [age] via GitHub
  • Re: [I] Multi-row `CREATE` followed by a second `CREATE` reports `vertex assigned to variable n0 was deleted` [age] via GitHub
  • Re: [I] Multi-row `CREATE` followed by a second `CREATE` reports `vertex assigned to variable n0 was deleted` [age] via GitHub
• [I] write/read rescan is rejected inside one Cypher query [age] via GitHub
  • Re: [I] write/read rescan is rejected inside one Cypher query [age] via GitHub
• [I] CASE WHEN <numeric aggregate> IS NULL THEN null ELSE <numeric aggregate> END` fails with a boolean type error [age] via GitHub
  • Re: [I] CASE WHEN <numeric aggregate> IS NULL THEN null ELSE <numeric aggregate> END` fails with a boolean type error [age] via GitHub
• [I] Shameless plug: A networkit wrapper for AGE [age] via GitHub
• [I] Different query results in age-views [age-viewer] via GitHub
• [Review]Cypher write-executor performance improvements (GitHub PRs #2517 and #2486) crdv7
• Question about Intra-Query Parallelism for Cypher in Apache AGE Parastoo Kafili
  • Re: Question about Intra-Query Parallelism for Cypher in Apache AGE Greg Felice
• [I] TRUNCATE fails with `schema "ag_catalog" does not exist` in databases without AGE, when AGE is in shared_preload_libraries [age] via GitHub
  • Re: [I] TRUNCATE fails with `schema "ag_catalog" does not exist` in databases without AGE, when AGE is in shared_preload_libraries [age] via GitHub
• [I] age_create_barbell_graph() crashes the backend (SIGSEGV) when node_label is left at its default [age] via GitHub
  • Re: [I] age_create_barbell_graph() crashes the backend (SIGSEGV) when node_label is left at its default [age] via GitHub
• [I] `reduce()`/list comprehension in a `LIMIT` or `SKIP` clause raises internal error `unsupported SubLink` (0A000) [age] via GitHub
  • Re: [I] `reduce()`/list comprehension in a `LIMIT` or `SKIP` clause raises internal error `unsupported SubLink` (0A000) [age] via GitHub
• [I] List predicate (`ALL`/`any`/`none`/`single`) over node values in a `WHERE` clause raises internal error `no relation entry for relid` (XX000) [age] via GitHub
  • Re: [I] List predicate (`ALL`/`any`/`none`/`single`) over node values in a `WHERE` clause raises internal error `no relation entry for relid` (XX000) [age] via GitHub
• [I] Integer modulo (%) by a zero divisor errors with `floating-point exception` (22P01) instead of `division by zero` [age] via GitHub
  • Re: [I] Integer modulo (%) by a zero divisor errors with `floating-point exception` (22P01) instead of `division by zero` [age] via GitHub
  • Re: [I] Integer modulo (%) by a zero divisor errors with `floating-point exception` (22P01) instead of `division by zero` [age] via GitHub
  • Re: [I] Integer modulo (%) by a zero divisor errors with `floating-point exception` (22P01) instead of `division by zero` [age] via GitHub
• [I] `id(n)` after rebinding the same variable across a `WITH` errors with `age_id(_ag_label_vertex) does not exist` [age] via GitHub
  • Re: [I] `id(n)` after rebinding the same variable across a `WITH` errors with `age_id(_ag_label_vertex) does not exist` [age] via GitHub
• [I] `UNION` of a boolean expression and a constant literal fails: `UNION types boolean and agtype cannot be matched` [age] via GitHub
  • Re: [I] `UNION` of a boolean expression and a constant literal fails: `UNION types boolean and agtype cannot be matched` [age] via GitHub
• [I] `coalesce()` with a boolean expression and a constant literal fails: COALESCE types boolean and agtype cannot be matched [age] via GitHub
  • Re: [I] `coalesce()` with a boolean expression and a constant literal fails: COALESCE types boolean and agtype cannot be matched [age] via GitHub
• [I] `EXISTS { }` in a `WHERE` after a write clause crashes (segfault) the backend [age] via GitHub
  • Re: [I] `EXISTS { }` in a `WHERE` after a write clause crashes (segfault) the backend [age] via GitHub
• [I] EXISTS { } in a WHERE after a write clause crashes (segfault) the backend [age] via GitHub
  • Re: [I] EXISTS { } in a WHERE after a write clause crashes (segfault) the backend [age] via GitHub
• [I] Server crashes (segfault) when a MATCH pattern property-map value is a correlated `EXISTS { }` subquery containing an aggregate [age] via GitHub
  • Re: [I] Server crashes (segfault) when a MATCH pattern property-map value is a correlated `EXISTS { }` subquery containing an aggregate [age] via GitHub
• [I] `CREATE` a relationship whose endpoint is `NULL` crashes (Segfault) the backend [age] via GitHub
  • Re: [I] `CREATE` a relationship whose endpoint is `NULL` crashes (Segfault) the backend [age] via GitHub
• [I] create_graph() fails when ag_catalog is not in search_path: operator class "graphid_ops" does not exist [age] via GitHub
• [I] Cypher fails after pg_dump/restore: ag_graph.graphid is a bare oid and keeps the source database's value [age] via GitHub
• [I] Windows prebuilt binaries for PG16 (AGE 1.5.0) — community builds gone, request for an official or tracked build [age] via GitHub
• [I] Server crashes (segfault) on `cypher(CREATE ...)` inside SQL `WHERE NOT EXISTS` with a nested `cypher(MATCH ...)` subquery [age] via GitHub
  • Re: [I] Server crashes (segfault) on `cypher(CREATE ...)` inside SQL `WHERE NOT EXISTS` with a nested `cypher(MATCH ...)` subquery [age] via GitHub
• [I] Segfault: `id()` compared against a variable-bound list crashes the backend (`master` and PG18 1.8.0) [age] via GitHub
• [RESULT][VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 John Gemignani
• [I] Writes are silently discarded when a later clause reads a label whose table is empty (DML CustomScan never executed) [age] via GitHub
  • Re: [I] Writes are silently discarded when a later clause reads a label whose table is empty (DML CustomScan never executed) [age] via GitHub
  • Re: [I] Writes are silently discarded when a later clause reads a label whose table is empty (DML CustomScan never executed) [age] via GitHub
• [I] Nodes created earlier in a multi-part query are not bound by a later `OPTIONAL MATCH` [age] via GitHub
  • Re: [I] Nodes created earlier in a multi-part query are not bound by a later `OPTIONAL MATCH` [age] via GitHub
  • Re: [I] Nodes created earlier in a multi-part query are not bound by a later `OPTIONAL MATCH` [age] via GitHub
• [I] `CREATE` operations are silently discarded in a multi-part query containing a variable-length `MATCH` [age] via GitHub
  • Re: [I] `CREATE` operations are silently discarded in a multi-part query containing a variable-length `MATCH` [age] via GitHub
  • Re: [I] `CREATE` operations are silently discarded in a multi-part query containing a variable-length `MATCH` [age] via GitHub
• [I] `CREATE` operations are silently discarded in a multi-part write-and-read query [age] via GitHub
  • Re: [I] `CREATE` operations are silently discarded in a multi-part write-and-read query [age] via GitHub
  • Re: [I] `CREATE` operations are silently discarded in a multi-part write-and-read query [age] via GitHub
• [I] Relationship created earlier in the same query is not matched after `WITH` and `UNWIND` [age] via GitHub
  • Re: [I] Relationship created earlier in the same query is not matched after `WITH` and `UNWIND` [age] via GitHub
• [I] Clarify SET semantics when one entity appears in multiple result rows [age] via GitHub
  • Re: [I] Clarify SET semantics when one entity appears in multiple result rows [age] via GitHub
  • Re: [I] Clarify SET semantics when one entity appears in multiple result rows [age] via GitHub
• [I] Same-row alias updates can overwrite earlier changes to the same entity [age] via GitHub
• [I] Avoid redundant entity lookups in writable Cypher clauses [age] via GitHub
• [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 John Gemignani
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 Muhammad Shoaib
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 Greg Felice
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 Taha Naveed
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 Greg Felice
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 Eya Badal
  • Re: [VOTE] Apache AGE 1.8.0 Release for PostgreSQL 18 John Gemignani
• [I] A redundant type(r) = 'P' check makes a statically typed relationship query about 6x slower [age] via GitHub
  • Re: [I] A redundant type(r) = 'P' check makes a statically typed relationship query about 6x slower [age] via GitHub
• [I] A redundant length(p) = 2 check makes a fixed two-hop path about 11x slower [age] via GitHub
• [I] Relationship-type alternation [:A|B] scans all edge label tables instead of only the listed labels [age] via GitHub
• [I] PG19: error: expected identifier or ‘(’ before ‘void’ [age] via GitHub
  • Re: [I] PG19: error: expected identifier or ‘(’ before ‘void’ [age] via GitHub
  • Re: [I] PG19: error: expected identifier or ‘(’ before ‘void’ [age] via GitHub
  • Re: [I] PG19: error: expected identifier or ‘(’ before ‘void’ [age] via GitHub
  • Re: [I] PG19: error: expected identifier or ‘(’ before ‘void’ [age] via GitHub
• Re: [I] Two typos on your README / GitHub landing page [age] via GitHub
• [DISCUSS] Apache AGE 1.8.0 Release for PostgreSQL 18 John Gemignani
  • Re: [DISCUSS] Apache AGE 1.8.0 Release for PostgreSQL 18 John Gemignani
• [DISCUSS] Apache AGE 1.8.0 Release for PostgreSQL 19 John Gemignani
  • Re: [DISCUSS] Apache AGE 1.8.0 Release for PostgreSQL 19 John Gemignani
• [I] Dead links in drivers/golang/README.md, drivers/golang/TYPES.md, drivers/jdbc/README.md [age] via GitHub
  • Re: [I] Dead links in drivers/golang/README.md, drivers/golang/TYPES.md, drivers/jdbc/README.md [age] via GitHub
• [I] Segfault: DETACH DELETE of an edge-connected vertex under FORCE ROW LEVEL SECURITY as a non-superuser [age] via GitHub
  • Re: [I] Segfault: DETACH DELETE of an edge-connected vertex under FORCE ROW LEVEL SECURITY as a non-superuser [age] via GitHub
  • Re: [I] Segfault: DETACH DELETE of an edge-connected vertex under FORCE ROW LEVEL SECURITY as a non-superuser [age] via GitHub
• [I] Standalone `OPTIONAL MATCH` drops the initial input row when the pattern has no match [age] via GitHub
• [I] `tail([1])` and `tail([])` return `null` instead of `[]` [age] via GitHub
• [I] 64-bit integer arithmetic overflow silently wraps around instead of failing [age] via GitHub
• [I] Concurrent creation of the same label races and fails with "duplicate key value violates unique constraint pg_class_relname_nsp_index" [age] via GitHub
• [I] Cache ResultRelInfo per label in apply_update_list to avoid per-row generated-expr rebuild on SET [age] via GitHub
• [I] Crash (Segmentation Fault) when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
  • Re: [I] [Segmentation Fault] when creating graph node whose vertex label table has GENERATED ALWAYS columns [age] via GitHub
• [I] load_labels_from_file and load_edges_from_file functions undocumented use of comma as delimiter via PostgreSQL COPY default, causes data corruption on labels and segfault on edges [age] via GitHub
  • Re: [I] load_labels_from_file and load_edges_from_file functions undocumented use of comma as delimiter via PostgreSQL COPY default, causes data corruption on labels and segfault on edges [age] via GitHub
  • Re: [I] load_labels_from_file and load_edges_from_file functions undocumented use of comma as delimiter via PostgreSQL COPY default, causes data corruption on labels and segfault on edges [age] via GitHub
• [I] Mnemosyne OS — Production use case: AI agent memory with Apache AGE knowledge graph [age] via GitHub
• [I] Single-node labeled pattern (a:Label) does not filter by label (vertex-only EXISTS skips label quals) [age] via GitHub
  • Re: [I] Single-node labeled pattern (a:Label) does not filter by label (vertex-only EXISTS skips label quals) [age] via GitHub
  • Re: [I] Single-node labeled pattern (a:Label) does not filter by label (vertex-only EXISTS skips label quals) [age] via GitHub
  • Re: [I] Single-node labeled pattern (a:Label) does not filter by label (vertex-only EXISTS skips label quals) [age] via GitHub
• [I] pthread_mutex in manage_GRAPH_global_contexts causes permanent self-deadlock on VLE queries [age] via GitHub
  • Re: [I] pthread_mutex in manage_GRAPH_global_contexts causes permanent self-deadlock on VLE queries [age] via GitHub
• [DISCUSS] Placement and PyPI ownership for a LlamaIndex PropertyGraphStore integration (re: #1783) Prashant Kumar via dev
• [PR] docs(RETURN): document pattern expressions in projections [age-website] via GitHub
  • Re: [PR] docs(RETURN): document pattern expressions in projections [age-website] via GitHub
• [I] Missed optimization: NULL contradiction disjunct adds Apache AGE filter rows [age] via GitHub
  • Re: [I] Missed optimization: NULL contradiction disjunct adds Apache AGE filter rows [age] via GitHub
  • Re: [I] Missed optimization: NULL contradiction disjunct adds Apache AGE filter rows [age] via GitHub
• [PR] Bump idna from 3.7 to 3.15 [age-website] via GitHub
  • Re: [PR] Bump idna from 3.7 to 3.15 [age-website] via GitHub
• [D] GraphML Support for AGE [age] via GitHub
• [PR] Bump urllib3 from 2.6.3 to 2.7.0 [age-website] via GitHub
  • Re: [PR] Bump urllib3 from 2.6.3 to 2.7.0 [age-website] via GitHub
• [I] Python driver: Double quotes at the end of string values are wrongfully removed [age] via GitHub
  • Re: [I] Python driver: Double quotes at the end of string values are wrongfully removed [age] via GitHub
• [I] Cypher keyword-named aliases cannot be referenced back as variables [age] via GitHub
  • Re: [I] Cypher keyword-named aliases cannot be referenced back as variables [age] via GitHub
  • Re: [I] Cypher keyword-named aliases cannot be referenced back as variables [age] via GitHub
  • Re: [I] Cypher keyword-named aliases cannot be referenced back as variables [age] via GitHub
  • Re: [I] Cypher keyword-named aliases cannot be referenced back as variables [age] via GitHub
• Re: [I] Usind reserved keywords as aliases in Cypher queries [age] via GitHub
  • Re: [I] Usind reserved keywords as aliases in Cypher queries [age] via GitHub
• [PR] Fix UNWIND [null] count() regression (#2383) — PR #2411 Prashant Kumar via dev
• [I] Latent NULL p_nscolumns in OPTIONAL MATCH lateral-join ParseNamespaceItem [age] via GitHub
  • Re: [I] Latent NULL p_nscolumns in OPTIONAL MATCH lateral-join ParseNamespaceItem [age] via GitHub
  • Re: [I] Latent NULL p_nscolumns in OPTIONAL MATCH lateral-join ParseNamespaceItem [age] via GitHub
  • Re: [I] Latent NULL p_nscolumns in OPTIONAL MATCH lateral-join ParseNamespaceItem [age] via GitHub
• [I] load age on restricted user [age-viewer] via GitHub
• [I] A `WHERE EXISTS { ... }` subquery may crash Apache AGE when it contains both: [age] via GitHub
• [I] List comprehension over a collected node list may fail when accessing node properties. [age] via GitHub
  • Re: [I] List comprehension over a collected node list may fail when accessing node properties. [age] via GitHub
• [I] List-comprehension `WHERE` filters may mishandle `null` elements. [age] via GitHub
  • Re: [I] List-comprehension `WHERE` filters may mishandle `null` elements. [age] via GitHub
• [I] Map literals may drop keys whose values are `null`. [age] via GitHub
  • Re: [I] Map literals may drop keys whose values are `null`. [age] via GitHub
• [I] List slicing may return a concrete sublist on Apache AGE when either the slice start bound or end bound is `null`. [age] via GitHub
• [I] List-comprehension projection over a `null` element may produce a nested list instead of `null`. [age] via GitHub
  • Re: [I] List-comprehension projection over a `null` element may produce a nested list instead of `null`. [age] via GitHub
• [I] `MATCH` may fail to see nodes that were created earlier in the same Cypher query after a `WITH` boundary. [age] via GitHub
• [I] When a query has multiple input rows, creating a node into a variable and then immediately creating a relationship to that variable may fail with: [age] via GitHub
• [I] `ORDER BY` may fail on Apache AGE when it references a property of a node value returned under an alias. [age] via GitHub
• [I] Order comparisons between values of different types may return a boolean instead of `null`. [age] via GitHub
• [I] `substring()` may crash Apache AGE when its start-offset argument is `null`. [age] via GitHub
  • Re: [I] `substring()` may crash Apache AGE when its start-offset argument is `null`. [age] via GitHub
• [I] `sum(...)` may mishandle `null` inputs. [age] via GitHub
• [I] `tail()` may return `null` on Apache AGE when the input list has length `0` or `1`. [age] via GitHub
  • Re: [I] `tail()` may return `null` on Apache AGE when the input list has length `0` or `1`. [age] via GitHub

• Earlier messages