Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Allow external recovery_config_directory

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Date: 2013-03-28 01:00:43
Message-ID: CAB7nPqQucfcpL+AHY+YOGfiqzxwtsYSx=xmqt3rZOaZdemFc_w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Thu, Mar 28, 2013 at 6:05 AM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com
> wrote:

> What exactly was wrong with pg_basebackup -R, without
> recovery_config_directory?
>
pg_basebackup -R generates automatically recovery.conf inside data folder,
so if
recovery_config_directory is specified the slave startup will fail.
The same problem exists also with the case where a tarball is generated for
base backup.
Such limitations should be specified in the docs at least.
-- 
Michael

In response to

pgsql-hackers by date

Next:From: Josh BerkusDate: 2013-03-28 01:06:07
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)
Previous:From: Tom LaneDate: 2013-03-28 00:04:55
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)

pgsql-committers by date

Next:From: Andrew DunstanDate: 2013-03-28 01:29:17
Subject: Re: pgsql: Set recovery_config_directory for EXEC_BACKEND.
Previous:From: Tom LaneDate: 2013-03-27 22:51:27
Subject: pgsql: Reset OpenSSL randomness state in each postmaster childprocess.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group