Nils Dijk b87fbcbf79 Shard moves/isolate report LSN's in lsn format (#7227) ... DESCRIPTION: Shard moves/isolate report LSN's in lsn format While investigating an issue with our catchup mechanism on certain postgres versions we noticed we print LSN's in the format of the native long type. This is an uncommon representation for LSN's in postgres logs. This patch changes the output of our log message to go from the long type representation to the native LSN type representation. Making it easier for postgres users to recognize and compare LSN's with other related reports. example of new output: ``` 2023-09-25 17:28:47.544 CEST [11345] LOG: The LSN of the target subscriptions on node localhost:9701 have increased from 0/0 to 0/E1ED20F8 at 2023-09-25 17:28:47.544165+02 where the source LSN is 1/415DCAD0 ```		2023-09-26 13:47:50 +02:00
..
multi_logical_replication.c	Shard moves/isolate report LSN's in lsn format (#7227)	2023-09-26 13:47:50 +02:00