| From: | Yogesh Jadhav <pgyogesh(at)outlook(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Tide <paveltide(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: suppress empty archive_command warning message |
| Date: | 2021-04-25 08:11:58 |
| Message-ID: | PS2PR03MB370260F10EA97D77B26FDE1AC4439@PS2PR03MB3702.apcprd03.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Greetings,
Why would anyone want to set archive_mode on and empty archive_command?
Thanks,
Yogesh
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Tide | 2021-04-25 13:33:54 | Re: suppress empty archive_command warning message |
| Previous Message | Stephen Frost | 2021-04-23 19:38:09 | Re: suppress empty archive_command warning message |