MIME-Version: 1.0
References: 
 <CAAnkphW8RpmwodKyjQhT+6jaOSLG=ERd7n-9DHr0CLRSY2W+mg@mail.gmail.com>
 <20210423191750.GA7630@momjian.us>
 <20210423193809.GL20766@tamriel.snowman.net>
 <PS2PR03MB370260F10EA97D77B26FDE1AC4439@PS2PR03MB3702.apcprd03.prod.outlook.com>
 <CAAnkphU200qFbKLVOZnwccvOu8WSPUm5_32iuWTu-ZdPRQOkYw@mail.gmail.com>
 <20210425180804.GQ20766@tamriel.snowman.net>
In-Reply-To: <20210425180804.GQ20766@tamriel.snowman.net>
From: Pavel Tide <paveltide@gmail.com>
Date: Mon, 26 Apr 2021 19:29:16 +0200
Message-ID: 
 <CAAnkphUSwjBYfiZO2w5+AwPftuY-vWQr8Br1eaWbfuCh=caX6A@mail.gmail.com>
Subject: Re: suppress empty archive_command warning message
To: Stephen Frost <sfrost@snowman.net>
Cc: Yogesh Jadhav <pgyogesh@outlook.com>, Bruce Momjian <bruce@momjian.us>,
	pgsql-novice@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAAnkphUSwjBYfiZO2w5%2BAwPftuY-vWQr8Br1eaWbfuCh%3DcaX6A%40mail.gmail.com>
Precedence: bulk

On Sun, Apr 25, 2021 at 8:08 PM Stephen Frost <sfrost@snowman.net> wrote:
>
> Greetings,
>
> * Pavel Tide (paveltide@gmail.com) wrote:
> > Right, but /bin/false will make pgsql to retry the command again and again
> > and that will throw warnings as well (AFAIK).
>
> It'll say it's retrying, sure.

Right, but after 3 retries (1 second between them) it will give a
warning anyway:

WARNING: archiving write-ahead log file "000000030000000500000084"
failed too many times, will try again later

Which brings us back to the initial problem.

>
> > I would like to copy WALs once in every "X" minutes instead of copying them
> > continuously.
>
> PG is only going to call the archice command when you've written 16MB of
> WAL (unless you also have archive timeout set...).
>
> Maybe you can clarify your use-case as to why you only want to copy them
> once every 'X' minutes..?
>
> Thanks,
>
> Stephen

Sure.

We have many postgres servers so we would prefer our central server to
collect logs in packs, all at once, instead of the servers streaming
them continuously.

What if we put "sleep X" insude our archive command so that it will
wait until we are ready to process the bunch of logs? Is there any
limit for how long PG will wait for the command to return something?

Thanks