Always Output Data option is ignored in Postgres node on executeQuery operation [from N8N v0.237.0 - v1.x onwards]

[pbdco]

Hi @MutedJam thank you for your response!

I’ve seen the fix in that PR but unfortunately I cannot upgrade to v1.x because of this :

Entire node fail if one key value returns ERROR: no data, execute "node-name" node first

Same case for me Updated to v1 and 90% of my workflows broke because of this. Downgraded to 0.237.0 and will remain there possibly forever. I use this approach very much: in one expression look for 2 or more nodes output. The remaining value corresponds to the node that has been executed previously. I do not understand why this has been deprecated, it is so useful in so many scenarios. It simplifies the workflows and avoids redundacy very much. I hope that in som…

I was wondering if this fix could be backported to v0.2x or Postgres node v2… until the above behavior is fixed/changed in future 1.x versions…