On 11/10/21, 9:51 PM, "Bharath Rupireddy" <bharath.rupireddyforpostg...@gmail.com> wrote: > But for the snprintf(activitymsg, sizeof(activitymsg), "archiving %s", > xlog); we have elog(DEBUG1, "archived write-ahead log file \"%s\"", > xlog); after the archiving command. It is also good to have a similar > debug message before archive command execution, we can get to know > whether archive command is executed or not, if yes how much time did > it take etc.?
There is a DEBUG3 that emits "executing archive command..." prior to executing the archive command. > I'm not sure whether it is okay to do the following, for every of the > activitymsg, before the command execution, we have an elog(DEBUG1 > message and after the command execution another elog(DEBUG1 message. The general idea seems reasonable to me. Nathan
