ERROR: Connection pool of the database object has been destroyed. My n8n version, 1.1.1, is showing this error since versions prior to 1.0 Previously I managed to work around the situation by using a ‘set’ node before every Postgres node, but now it’s still intermittently presenting the error. us…

Share my flow: https://gist.githubusercontent.com/Jorgelig/5ec460d8704200bf892bbc3589d59376/raw/41376ccc5dedf630a4adb8bd83962671dda6c0c9/postgresql_n8n.json [image] I’ve tried to batch items even 50 at a time and it keeps failing.

Facing same issue with my workflows aswell, issue started in 1.1.1

Hey @Roney_Dsilva , Can you share a workflow that reproduces this issue? So far I am not able to reproduce it, I am aware that this has been fixed by another user by tweaking the database settings for the usage so it would be worth looking at that as well if it is an option.

Hi @Jon [image] Doesn’t happen every time though, its happen like for alternate executions The current flow where am getting this is quite complex, will try to replicate it with a simpler flow and share the same with you

When it happens is it usually with single items like that? Which version of n8n are you running and is your Postgres instance from a cloud provider or is it a docker image?

HI @Jon It happens for Single item, n8n version is 1.1.1 Postgres is Docker image locally deployed in same network as n8n postgres:12.4 same of postgres:14

Hi @Jon I noticed this happening quite frequently when you are trying to perform multiple parallel db actions. eg: if you have an active workflow running in the background and try to do something else in your current workflow, you get this error. It sounds like some keep-alive issue that is overl…

Hey @MayurVirkar , Interesting, We don’t generally keep the connection alive and each item query will create a new one but the idea of running the same workflow at the same time might be the key I will give that a bash on Monday.

Hi @Jon Were you able to replicate it? We are facing it quite frequently. Also, if you need any assistance in debugging the issue, kindly let us know. We can give you any data that’s required. Such as extended logs etc etc. We are facing it in every 2 out of 3 runs.

He managed to replicate today, check it out here. [image] Serious error in postgres node Questions Morning, It looks like there are different causes, I suspect the issue is down to a mix of things and the configuration of postgres to be able to handle th…

POSTGRES ERROR: Connection pool of the database object has been destroyed

Questions

admdiegolima August 21, 2023, 3:55pm 22

He managed to replicate today, check it out here.

Topic		Replies	Views
Serious error in postgres node Questions postgres	14	1904	September 6, 2023
Problems with Postgres Memory Node in n8n - cannot use pool Questions postgres	23	2902	January 20, 2025
Postgres Connection Error - "sorry, too many clients already" Questions	24	3323	June 12, 2025
I am getting an error in a new postgres node when using "insert or update" operation Questions credentials , node	42	3665	September 6, 2023
Postgres node - Called end on pool more than once Questions postgres	38	2629	October 18, 2023

POSTGRES ERROR: Connection pool of the database object has been destroyed

Related topics