agensgraph
agensgraph copied to clipboard
Segmentation fault on MERGE query
How to reproduce
drop graph if exists issue737 cascade;
create graph issue737;
SET graph_path = issue737;
postgres=# MATCH (n0) MERGE (n0 {k:1}) RETURN count(n0);
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
The connection to the server was lost. Attempting reset: Failed.
Server log
2025-06-25 09:02:55.263 KST [200622] STATEMENT: SET graph_path = issue737;
2025-06-25 09:03:01.120 KST [181780] DEBUG: server process (PID 200622) was terminated by signal 11: Segmentation fault
2025-06-25 09:03:01.120 KST [181780] DETAIL: Failed process was running: MATCH (n0) MERGE (n0 {k:1}) RETURN count(n0);
2025-06-25 09:03:01.120 KST [181780] LOG: server process (PID 200622) was terminated by signal 11: Segmentation fault
2025-06-25 09:03:01.120 KST [181780] DETAIL: Failed process was running: MATCH (n0) MERGE (n0 {k:1}) RETURN count(n0);
2025-06-25 09:03:01.120 KST [181780] LOG: terminating any other active server processes
2025-06-25 09:03:01.120 KST [181780] DEBUG: sending SIGQUIT to process 200406
2025-06-25 09:03:01.120 KST [181780] DEBUG: sending SIGQUIT to process 200403
2025-06-25 09:03:01.120 KST [181780] DEBUG: sending SIGQUIT to process 200402
2025-06-25 09:03:01.120 KST [181780] DEBUG: sending SIGQUIT to process 200404
2025-06-25 09:03:01.120 KST [181780] DEBUG: sending SIGQUIT to process 200405
2025-06-25 09:03:01.121 KST [181780] DEBUG: forked new backend, pid=200892 socket=9
2025-06-25 09:03:01.121 KST [200892] FATAL: the database system is in recovery mode
2025-06-25 09:03:01.122 KST [181780] DEBUG: server process (PID 200892) exited with exit code 1
2025-06-25 09:03:01.122 KST [181780] LOG: all server processes terminated; reinitializing
...
Some recovery logs are below...
Currently, I'm shortly think that server should not be crashed by the segfault but printing some error text.