| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-03-28 01:29:17 | Re: pgsql: Set recovery_config_directory for EXEC_BACKEND. |
| Previous Message | Tom Lane | 2013-03-27 22:51:27 | pgsql: Reset OpenSSL randomness state in each postmaster child process. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-03-28 01:06:07 | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
| Previous Message | Tom Lane | 2013-03-28 00:04:55 | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |