From: Stephen Frost <sfrost@snowman.net>
To: Praveen Kumar K S <praveenssit@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: [HELP] Issue with standby server using WAL archive
Date: Thu, 2 Jul 2020 11:54:33 -0400
Message-ID: <20200702155433.GT3125@tamriel.snowman.net> (raw)
In-Reply-To: <CANSiNp4MiEBrOgK3s-Ljw7poNFeb8_oL9HuTt-hZfhqYiendFQ@mail.gmail.com>
References: <CANSiNp6iAACN_4HjHUqFEmTOd_0QvdBiE5W1XXjwFniNwUWAYQ@mail.gmail.com>
<20200702141444.GJ3125@tamriel.snowman.net>
<CANSiNp6y1tm08Z=mDj6RL33iUjM1ozw6DtKY7Dz6FofxLvFNqA@mail.gmail.com>
<20200702152608.GQ3125@tamriel.snowman.net>
<CANSiNp4MiEBrOgK3s-Ljw7poNFeb8_oL9HuTt-hZfhqYiendFQ@mail.gmail.com>
Greetings,
* Praveen Kumar K S (praveenssit@gmail.com) wrote:
> I'm seeing below error on pg3 (DR server) in log. Is this expected ?
> *cp: cannot stat '/mnt/server/archivedir/00000001000000000000000D': No such
> file or directory*
Yes, that's expected, the replica will constantly attempt to get the
next WAL segment to replay, unless you have streaming replication
configured. There's nothing wrong with that.
> On master, I see below info. I would like to know why the WALs are not
> being archived.
The WAL file isn't going to be archived until PG is done writing into
it, which won't happen until there's been ~16MB of write activity on the
database. If you want WAL to be archived more frequently even if the
segment isn't full then you should look at the archive_timeout option.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sfrost@snowman.net, praveenssit@gmail.com
Subject: Re: [HELP] Issue with standby server using WAL archive
In-Reply-To: <20200702155433.GT3125@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox