overy has begun.
>> Recovery has not begun. Without the change, the recovery will not start. So,
>do I have to do a reload, or restart, for the parameter to take effect? The
>situation is - master is up and running, slave is up and running. I made a
>change to recovery.conf. How can I make slave '
On Thu, Jul 11, 2013 at 6:19 PM, Jayadevan M
wrote:
> Hi,
>> wrote:
>>> I have postgresql streaming replication set up. I forgot to add an
>>> entry for trigger_file in recovery.conf. So I added that entry and did
>>> a pg_ctl reload.
>>Recovery parameters are not GUC parameters, so doing a parame
Hi,
> wrote:
>> I have postgresql streaming replication set up. I forgot to add an
>> entry for trigger_file in recovery.conf. So I added that entry and did
>> a pg_ctl reload.
>Recovery parameters are not GUC parameters, so doing a parameter reload
>has no effect. Also, such parameters cannot be c
Hi Jayadevan,
Il 11/07/2013 09:39, Jayadevan M ha scritto:
Hi,
I have postgresql streaming replication set up. I forgot to add an
entry for trigger_file in recovery.conf. So I added that entry and did
a pg_ctl reload. Is there a way to confirm that the entry has been
read by the server? Any
On Thu, Jul 11, 2013 at 4:39 PM, Jayadevan M
wrote:
> I have postgresql streaming replication set up. I forgot to add an entry for
> trigger_file in recovery.conf. So I added that entry and did a pg_ctl
> reload.
Recovery parameters are not GUC parameters, so doing a parameter
reload has no effect
