Bug #5313

PITR archiving bug

Added by Michael Vitale 05/14/2015 (almost 4 years) ago. Updated 10/22/2015 (over 3 years) ago.

Status:ClosedStart date:05/14/2015
Priority:NormalDue date:
Assignee:Eric Worden% Done:

0%

Category:-
Target version:-
Resolution:fixed

Description

In the cmd_archiver.ini file, if you don't specify the remote copy archive location with a trailing forward slash at the end, when you start to do WAL archiving, files will be created in the data directory of the slave, and the archive subdirectory will not be created. There is no such problem with or without the trailing forward slash for the local archive directory, l_archivedir.

To similulate the problem, set r_archivedir without a trailing slash, and make sure the $PGDATA/archive directory does not exist on the slave.
r_archivedir: /var/lib/postgresql/9.3/main/archive

To get it to run as expected, add the trailing slash and repeat the tests. Things work fine this way:
l_archivedir: /var/lib/postgresql/9.3/main/archive/

History

#1 Updated by Eric Worden 10/22/2015 (over 3 years) ago

  • Status changed from New to Closed
  • Assignee changed from Michael Vitale to Eric Worden
  • Resolution set to fixed

This issue affects the version in the tarball referenced in the wiki but not the current HEAD of master.

Eric

Also available in: Atom PDF