Re: suppress empty archive_command warning message

Greetings,

Please don't top-post on these lists.

* Yogesh Jadhav (pgyogesh(at)outlook(dot)com) wrote:
> Why would anyone want to set archive_mode on and empty archive_command?

Well, not very likely, which is why there's a warning sent out about it.

That said, when doing things like promoting a new node for a failover,
or maybe doing a restore to a new system for some kind of testing or
development work, etc, there could be reasons that you'd want archiving
enabled but not want the archive_command to actually be set (yet).

Thanks,

Stephen

> > On 24-Apr-2021, at 1:08 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> >
> > Greetings,
> >
> > * Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> >> On Fri, Apr 23, 2021 at 08:48:39PM +0200, Pavel Tide wrote:
> >>> Is there a way to suppress the WARNING that is thrown in PG logs if
> >>> archive_mode is enabled but the archive command is empty? Maybe some
> >>> configuration key which I have overlooked?
> >>
> >> Have you tried putting "/bin/true" in there, for non-Windows?
> >
> > Erm, that would cause all WAL to just be silently thrown away.. To have
> > the same behavior as having it be unset, you'd set it to '/bin/false'.
> >
> > Of course, which you want depends, but generally you should be using a
> > real archive command to archive your WAL, not throwing it away.
> >
> > Thanks,
> >
> > Stephen