On Fri, Nov 29, 2024 at 4:05 PM Hayato Kuroda (Fujitsu) <kuroda.hay...@fujitsu.com> wrote: > > 07. wait_for_publisher_status > > I think all calculations and checking in the function can be done even on the > walsender. Based on this, I come up with an idea to reduce the message size: > walsender can just send a status (boolean) whether there are any running > transactions > instead of oldest xid, next xid and their epoch. Or, it is more important to > reduce the > amount of calc. on publisher side? >
Won't it be tricky to implement this tracking on publisher side? Because we not only need to check that there is no running xact but also that the oldest_running_xact that was present last time when the status message arrived has finished. Won't this need more bookkeeping on publisher's side? -- With Regards, Amit Kapila.
