Postgres Query Parameters ... bug?

Questions
1

Describe the problem/error/question

Experiencing what seems to be a bug with postgres query parameters.
When I attempt to pass a JSON object through to a query the commas inside the object appear to be interfering with the parsing of the query parameters

image
image1821×566 61 KB

I haven’t changed how I’m using them so I wonder if it’s a bug that’s crept. I am self taught, so it’s quite possible I’m using an ill-advised technique that has somehow worked so far but is now breaking?

What is the error message (if any)?

The error I get when I use the query parameter as intended is “The input string ended unexpectedly.”:

image
image1797×558 61.9 KB

Please share your workflow

Happy to share the workflow if the screenshots aren’t enough, just not sure what happens to database access if I post a postgres node on here?

  • **n8n version:**1.53.1 (Cloud)
  • Database (default: SQLite):
  • **n8n EXECUTIONS_PROCESS setting (default: own, main): manual
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • **Operating system: windows & chrome
2

So I think I’ve figured out what the source of the issue is. It looks like a problem with the latest Postgres node (version 2.5).

I’ve copied v2.4 from another workflow and the query and parameters now work correctly (i.e. commas inside one parameter do not impact the parsing of the parameters themselves):

image
image1865×720 73.6 KB

3

Hi @jamescv

could you kindly share your workflow / dummy data → would like to reproduce this and confirm whether it’s a bug :slight_smile:

Thanks! :pray:

4

Hi Ria

Here you go:

5

I have the same issue still, with Postgres Node v2.5 indeed. How to downgrade to v2.4?

6

Hi all,

I have raised an internal bug ticket for this and will post here for an update.
:pray:

In the meantime, you can continue to use the old postgres node v 2.4

1 Like
8

I have the same issue with MySQL node version 2.4 (Latest), even a string like “Hello, here is my name” is breaking the code.

Any news about your internal ticket?

9

I’m getting this bug as well on 2.5. Rolling back to 2.4 fixed it.

10

Getting this aswell on 1.67.1

11

Is there an update on this? I’m getting this error on n8n version 1.72.1

12

I haven’t seen a fix, I would assume until you see the Postgres node update to v2.6, that it won’t have been addressed.

13

This is no longer an issue on the latest n8n version which, at the time of writing, is 1.81.4.