Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming - Mailing list pgsql-bugs

From Zane Duffield
Subject Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
Date
Msg-id CACMiCkUJ6Pb7P4MdRB8g-YksXAgypZ7ZRYUHQ9u7nU-WiTxsLg@mail.gmail.com
Whole thread Raw
In response to Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
List pgsql-bugs
Sorry for the late reply.

After some more testing, we are going ahead with `streaming = parallel`, with the change to reset `lock_timeout` to the default.

No, as per my understanding it is because parallel apply worker
exiting due to lock_timeout set in the test. Ideally, the patch
proposed by Kuroda-San should show in LOGs that the parallel worker is
exiting due to lock_timeout. Can you try that once?

I don't think I'll have time to compile a patched version and run the tests again, sorry. Have this information in the log probably would have made it easier to work this whole problem out, though, so I hope someone else can test out the change and get it merged.

Thanks for your help Amit, Hou-san, and Hayato-san.

Zane
 

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Next
From: David Rowley
Date:
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos