Server crashes when trying to set a new property

[turicas]

Hi! First of all, thanks for creating this project, it's pretty useful. :)

I'm running AgensGraph v2.1.1 via docker and the server is terminating abnormally when I try to set a property value (this property didn't exist before). I have the label company with 37M+ nodes, if I execute a [...] RETURN n; query it works, if I execute a [...] SET n.prop = value; for the same MATCH query it crashes (this SET would affect 122k+ nodes). The idea of this query is to set the holding property as true in all companies that are partners in other companies but don't have any companies has partners of them.

I've tried everything using psql (is it required to use the AgensGraph CLI?), you can see the commands/results below:

psql (11.3 (Debian 11.3-1), server 10.4)
Type "help" for help.

agens=# set graph_path = partner;
SET
agens=# \timing
Timing is on.
agens=# MATCH (c:company)-[:is_partner]->(:company)
WHERE NOT exists((:company)-[:is_partner]->(c))
RETURN DISTINCT(c);
Time: 21446.111 ms (00:21.446) <- 122619 rows returned here
agens=# MATCH (c:company)-[:is_partner]->(:company)
WHERE NOT exists((:company)-[:is_partner]->(c))
SET c.holding = true;
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: Succeeded.
Time: 19042.115 ms (00:19.042)

Everytime I've tried it crashes after more or less 20 seconds.

[jrgemignani]

Hi, and thank you for using AgensGraph! I have a few questions in order to look deeper into the issue,...

• Are there any specific messages in the log file at the time of the crash?

• What Docker image are you using? Is it the one we provide?

• What are the memory settings in postgresql.conf?

Additionally, you can try upping the memory settings and restarting AgensGraph to see if that corrects the issue.

Thanks! john