With PostgreSQL target, big transaction replication resulting with a timeout (SqlState: 57014)

[JSCHRANZ]

Hi,

We have a replication task with Postgresql v17 as target endpoint working without issues for few days.
However, since this weekend, the task is looping on the same "timout" issue (Target table contains billions of rows):

00011719: 2026-10-03T05:42:34 [SORTER          ]I:  Task is running  (sorter.c:714)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Error in bulk, bulk state: bulk confirmed record id - '476716', bulk last record id - '404495777', confirmed record id - '396263857', sorter confirmed record id - '396263857'  (bulk_apply.c:2511)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Failed (retcode -1) to execute statement: 'UPDATE <...>' [1022502]  (ar_odbc_stmt.c:2852)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  RetCode: SQL_ERROR  SqlState: 57014 NativeError: 1 Message: ERROR: canceling statement due to statement timeout;
Error while executing the query [1022502]  (ar_odbc_stmt.c:2858)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Failed to execute update statement.

The timeout seems to happen on the Database side every 25 minutes:

026-10-03 06:46:30 CEST **** user=****, db=****, client=****, appli=QlikReplicate/2025.11 (postgresql), sessionid=**** ERROR:  canceling statement due to statement timeout
[...]
2026-10-03 05:50:23 CEST **** user=****, db=****, client=****, appli=QlikReplicate/2025.11 (postgresql), sessionid=**** ERROR: canceling statement due to statement timeout

We have tried to change this timeout on client side (Qlik connection) with below "Internal Parameters" set on the target endpoint:

• afterConnectScript => set statement_timeout=<0 et 86400000>
• executeTimeout => <0 et 86400>

But also on the role (user) used to connect with the database:

ALTER ROLE d9dext SET statement_timeout = <0 et 86400000>;
SELECT * FROM pg_db_role_setting;

Both didn't have any effect, the timeout still occuring every 25 minutes...

Any clues on what is happening? Seems to be the driver used by Qlik which is overriding the "statement_timeout" property...