Hello,
Thanks for your response.
But if you look at the output below, 00000001000000000000000D is already 16MB and new WAL are created. As per my understanding, 00000001000000000000000D should have been archived. Am I wrong here ?
postgres@pg1:~/9.6/main/pg_xlog$ ls -lrth
total 65M
-rw------- 1 postgres postgres 16M Jul 2 13:09 00000001000000000000000E
-rw------- 1 postgres postgres 16M Jul 2 13:13 00000001000000000000000F
-rw------- 1 postgres postgres 16M Jul 2 13:13 000000010000000000000010
-rw------- 1 postgres postgres 302 Jul 2 13:13 00000001000000000000000C.00000028.backup
drwx------ 2 postgres postgres 4.0K Jul 2 13:23 archive_status
-rw------- 1 postgres postgres 16M Jul 2 15:38 00000001000000000000000D
total 65M
-rw------- 1 postgres postgres 16M Jul 2 13:09 00000001000000000000000E
-rw------- 1 postgres postgres 16M Jul 2 13:13 00000001000000000000000F
-rw------- 1 postgres postgres 16M Jul 2 13:13 000000010000000000000010
-rw------- 1 postgres postgres 302 Jul 2 13:13 00000001000000000000000C.00000028.backup
drwx------ 2 postgres postgres 4.0K Jul 2 13:23 archive_status
-rw------- 1 postgres postgres 16M Jul 2 15:38 00000001000000000000000D
On Thu, Jul 2, 2020 at 9:26 PM Jeff Janes <jeff.janes@xxxxxxxxx> wrote:
On Thu, Jul 2, 2020 at 11:44 AM Praveen Kumar K S <praveenssit@xxxxxxxxx> wrote:Hello,Thanks for your response. I agree with all your suggestions.At this moment, I'm concerned about the WAL archiving.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 directoryYes, this is expected. That file has not been archived yet because the master is not done writing data to it yet. pg3 will keep retrying the command until the file shows up.Cheers,Jeff
--
Regards,
K S Praveen Kumar
M: +91-9986855625
M: +91-9986855625
