Postgress trigger over 8kb bug / no fallback mechanism

Questions
1

Describe the problem/error/question

As the title says, Postgres trigger node: the most standard one. If there is more than 8 KB of record size, it fails on the Postgres end, and it doesn’t even go to N8N. There is no fallback mechanism to identify that no data has been sent, other than on the PostgreSQL end.

What is the error message (if any)?

nope, read above why

Please share your workflow

Information on your n8n setup

  • n8n version: 2.3.4
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app):docker
  • Operating system:linux
1 Like
3

yeah the postgres trigger node uses postgres NOTIFY under the hood which has an 8kb payload limit - that’s a postgres limitation not an n8n thing. workaround is to just send the record ID through NOTIFY and then have n8n do a followup query with the Postgres node to fetch the full row data. you can set that up right after the trigger fires, something like:

```json

SELECT * FROM your_table WHERE id = {{ $json.id }}

```

not ideal but it works around the limit. lmk if you need help setting that up