Postgresql errors using docker v1.0.2

I’m getting loads of these errors since swapping over to the 1.x strand , I’m using 1.0.2

execution time: 1278
Attempt to read execution was blocked due to insufficient permissions
query is slow: COMMIT
execution time: 1426
query is slow: UPDATE "public"."execution_entity" SET "status" = $1 WHERE "id" = $2 -- PARAMETERS: ["running",66073]
execution time: 1403
query is slow: UPDATE "public"."execution_entity" SET "mode" = $1, "finished" = $2, "stoppedAt" = $3, "status" = $4 WHERE "id" = $5 -- PARAMETERS: ["manual",1,"2023-07-13T18:24:14.994Z","success",66073]
execution time: 1657
<--- Last few GCs --->
[9:0x7f2e9134c300] 22174398 ms: Scavenge 2035.8 (2070.5) -> 2033.8 (2071.0) MB, 15.0 / 0.0 ms  (average mu = 0.200, current mu = 0.159) allocation failure; 
[9:0x7f2e9134c300] 22174428 ms: Scavenge 2036.3 (2071.0) -> 2034.6 (2072.3) MB, 17.4 / 0.0 ms  (average mu = 0.200, current mu = 0.159) allocation failure; 
[9:0x7f2e9134c300] 22174463 ms: Scavenge 2037.5 (2072.3) -> 2035.6 (2081.3) MB, 18.3 / 0.0 ms  (average mu = 0.200, current mu = 0.159) allocation failure; 
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Aborted (core dumped)
Last session crashed
n8n ready on 0.0.0.0, port 5678
query is slow: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'public' AND "table_name" = 'migrations'
execution time: 1921
Initializing n8n process
query is slow: DELETE FROM "public"."execution_entity" WHERE "id" IN ($1, $2, $3, $4, $5, $6) -- PARAMETERS: ["62795","62789","62796","62800","62799","62802"]
execution time: 2043
<--- Last few GCs --->
[8:0x7f923434a300]   216538 ms: Scavenge 2038.2 (2072.1) -> 2036.1 (2072.6) MB, 14.2 / 0.0 ms  (average mu = 0.203, current mu = 0.167) allocation failure; 
[8:0x7f923434a300]   216565 ms: Scavenge 2038.7 (2072.6) -> 2037.0 (2073.9) MB, 17.1 / 0.0 ms  (average mu = 0.203, current mu = 0.167) allocation failure; 
[8:0x7f923434a300]   216591 ms: Scavenge 2039.9 (2073.9) -> 2038.0 (2082.9) MB, 16.3 / 0.0 ms  (average mu = 0.203, current mu = 0.167) allocation failure; 
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Aborted (core dumped)

any ideas?

im updating the .conf file to be more optimised and there are some other errors such as

2023-07-13 19:04:49.703 UTC [902] WARNING:  database "n8n" has a collation version mismatch
2023-07-13 19:04:49.703 UTC [902] DETAIL:  The database was created using collation version 2.31, but the operating system provides version 2.36.

so im about to try fix that too after a database dump/backup

i did this to get rid of the collation error

psql -U YOUR_USERNAME -W DATABASE_NAME

Once you’re connected, you can run the ALTER DATABASE command to refresh the collation:

ALTER DATABASE YOUR_DATABASE REFRESH COLLATION VERSION;

and restarted the docker container. those errors now gone

so far optimising postgresql.conf file has removed these errors for now.

1 Like

@RedPacketSec nice to see you worked it out, Oddly enough I didn’t run into any of that with my main install. Which Postgres version are you using?

The other error looks like it is probably memory related, Which version of n8n did you upgrade from?

i upgraded from latest to 1.0.2

postgres v15

I would have thought latest would have had the larger migration done, Not aware of anything in 1.x that could trigger that though.

I may do some more testing :slight_smile:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.