Hi, As discussed in [1], isn't it a better idea to add some of activity messages [2] such as recovery, archive, backup, streaming etc. to server logs at LOG level? They are currently being set into ps display which is good if the postgres is being run on a standalone box/VM where users can see the ps display, but it doesn't help much in case the postgres is being run on a cloud environment where users don't have access to ps display output. Moreover, the ps display is transient and will not help to analyze after an issue occurs.
Having the above messages in the server logs will be useful to understand how the system is/was doing/progressing with these (sometimes time-intensive) operations. Thoughts? [1] - https://www.postgresql.org/message-id/CALj2ACWE6D%2BbbKnA9tQ0d-pPN1n4xrsFPOmiURm2my3qt0w3OA%40mail.gmail.com [2] - snprintf(activitymsg, sizeof(activitymsg), "waiting for %s", snprintf(activitymsg, sizeof(activitymsg), "recovering %s", snprintf(activitymsg, sizeof(activitymsg), "performing %s%s%s", snprintf(activitymsg, sizeof(activitymsg), "archiving %s", xlog); snprintf(activitymsg, sizeof(activitymsg), "failed on %s", xlog); elog(DEBUG1, "archived write-ahead log file \"%s\"", xlog); snprintf(activitymsg, sizeof(activitymsg), "sending backup \"%s\"", snprintf(activitymsg, sizeof(activitymsg), "restarting at %X/%X", snprintf(activitymsg, sizeof(activitymsg), "streaming %X/%X", snprintf(activitymsg, sizeof(activitymsg), "streaming %X/%X", Regards, Bharath Rupireddy.
