On Wed, Dec 8, 2021 at 10:05 AM Michael Paquier <mich...@paquier.xyz> wrote: > > On Tue, Dec 07, 2021 at 06:28:24PM +0530, Bharath Rupireddy wrote: > > Upon thinking further, having at least the messages at LOG level [1] > > would be helpful to know what's happening with the system while in > > recovery. Although these messages at LOG level seem to be filling up > > the server logs, having a good log consumption and rotation mechanism > > (I'm sure every major postgres vendor would have one) would be > > sufficient to allay that concern. > > + ereport(LOG, > + (errmsg("recovering WAL segment \"%s\" from source \"%s\"", > + xlogfname, srcname))); > Isn't this approach an issue for translations? It seems to me that > terms like "stream" or "archive" had better be translated properly, > meaning that this needs a fully-constructed sentence.
Thanks for taking a look at the patch. How about the attached v4? I added a CF entry - https://commitfest.postgresql.org/36/3443/ Regards, Bharath Rupireddy.
v4-0001-add-log-messages-for-recovery.patch
Description: Binary data