| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display |
| Date: | 2021-11-11 15:11:49 |
| Message-ID: | 224D6A0D-D43C-4819-89AE-324818DC9A98@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/10/21, 9:51 PM, "Bharath Rupireddy" <bharath(dot)rupireddyforpostgres(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2021-11-11 15:18:16 | Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display |
| Previous Message | Tom Lane | 2021-11-11 14:52:52 | Re: Should AT TIME ZONE be volatile? |