Postgrestor bug - multiple databases

General
1

Hi all

This issue I can produce in my setup. Working with postgresql, this node is the best IMO. Has anyone found a fix/workaround this bug?

My approach would be to create a new NodeRED instance so I can "spread" my flows, avoiding the error, but isn´t a fix. I´ve discovered, when copy/pasting the flow to a new flow, the issue (as it is now) don´t occur.

2

Did you see someone posted a patch?

See this post

Replace your local js file with the contents of this one, restart node-red, give it a go.

Ps, looks like the author might have abandoned this node - that issue is from 2019.

3

I missed it on the the Github post and have tested it with no errors so far. Thx.

4

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