On Fri, Jan 20, 2023 at 2:47 PM shveta malik <shveta.ma...@gmail.com> wrote: > ... > 2) > Logging: > 2023-01-19 17:33:16.202 IST [404797] DEBUG: logical replication apply > delay: 19979 ms > 2023-01-19 17:33:26.212 IST [404797] DEBUG: logical replication apply > delay: 9969 ms > 2023-01-19 17:34:25.730 IST [404962] DEBUG: logical replication apply > delay: 179988 ms-->previous wait over, started for next txn > 2023-01-19 17:34:35.737 IST [404962] DEBUG: logical replication apply > delay: 169981 ms > 2023-01-19 17:34:45.746 IST [404962] DEBUG: logical replication apply > delay: 159972 ms > > Is there a way to distinguish between these logs? Maybe dumping xids > along-with? >
+1 Also, I was thinking of some other logging enhancements a) the message should say that this is the *remaining* time to left to wait. b) it might be convenient to know from the log what was the original min_apply_delay value in the 1st place. For example, the logs might look something like this: DEBUG: time-delayed replication for txid 1234, min_apply_delay = 160000 ms. Remaining wait time: 159972 ms DEBUG: time-delayed replication for txid 1234, min_apply_delay = 160000 ms. Remaining wait time: 142828 ms DEBUG: time-delayed replication for txid 1234, min_apply_delay = 160000 ms. Remaining wait time: 129994 ms DEBUG: time-delayed replication for txid 1234, min_apply_delay = 160000 ms. Remaining wait time: 110001 ms ... ------ Kind Regards, Peter Smith. Fujitsu Australia