Postgres Query Parameters break when a text parameter includes a comma

[DimaUndSo]

Bug Description

I refer here to the same issue that was already "Closed as not planned":
https://github.com/n8n-io/n8n/issues/14955

Closing this is ridiculous, please fix it, as you can't use the Postgres node properly right now with this error.
It needs weird workarounds, editing the text to remove the commas.. this is not the way it should be.

To Reproduce

1. Configure a Postgres node for the Execute Query operation.
2. Set the Query to use multiple parameters, e.g.: INSERT INTO your_table (text_col, timestamp_col) VALUES ($1, $2);
3. In the node "Options", add the "Query Parameters" field.
4. Enter an expression that evaluates to a comma-separated string where the first value contains a comma, e.g.:
5. {{ $json.textWithCommas }},{{ $json.ISOTimeStamp }}
6. Execute the node.

Expected behavior

The node should correctly parse the comma-separated string provided in the "Query Parameters" field. It should assign the full string "Text data, with a comma" to $1 and the string "2025-01-01T12:00:00Z" to $2, allowing the parameterised query to execute successfully against the database.

Operating System

Ubuntu Linux

n8n Version

1.97.1

Node.js Version

v20.19.0

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @DimaUndSo,

We have created an internal ticket to look into this which we will be tracking as "GHC-2548"

[xing5]

There's an issue with postgres text array field as well. When upsert completes, the array field in input data is mutated.

[DimaUndSo]

I fixed the error and made a pull request:
#16366

Hope its getting merged soon. Works now for me :)

[n8n-assistant]

Hi @DimaUndSo 👋

Thanks so much for your patience while we’ve been improving n8n. We know it’s taken some time to review this issue, and we’re currently updating our triage process to better keep up with our growth.

There have been a lot of improvements in recent releases, so we’d really appreciate it if you could check whether this issue still occurs in the latest release.

When you have a moment, please copy and paste the checklist below as a comment so our system can update the status automatically:

[ ] I have updated to the latest stable version of n8n [please specify version number] and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

If we don’t hear from you in the next 14 days this issue will be automatically closed, feel free to reopen - don’t forget to add the checklist above so that our automated systems notify us of the issue.

Thanks again for helping us keep n8n healthy and up-to-date 💚

[DimaUndSo]

I have updated to the latest stable version of n8n 1.117.3 and I am still experiencing this issue

[Psanyi89]

I have the same issue in the latest "Version: 1.117.3"