From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regarding(Read Replica in RDS) |
Date: | 2024-03-07 17:21:07 |
Message-ID: | CANzqJaC033MpHbZphPnkACd1X9NbCwCzOAXXoB8GxFGcxE6-LA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Mar 7, 2024 at 11:25 AM ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com>
wrote:
> Any other option.
>
Create a *second *fdw server (on the primary?), with the new host name.
That SERVER definition should be replicated to the Secondary, where you can
then use it.
> Bcz if I promote can I rollback again.
>
When you roll back... the altered server definition will also be rolled
back.
>
> Regards
> Rohit Sachdeva
>
> On Thu, 7 Mar, 2024, 8:00 pm Ron Johnson, <ronljohnsonjr(at)gmail(dot)com> wrote:
>
>> On Thu, Mar 7, 2024 at 9:26 AM Dan Smith <j(dot)daniel(dot)smith1(at)gmail(dot)com>
>> wrote:
>>
>>> You can promote a Read Replica via AWS CLI or AWS Web Console.
>>>
>>> Reference:
>>>
>>> -
>>> https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html#USER_ReadRepl.Promote
>>> -
>>> https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/promote-read-replica.html
>>>
>>> aws rds promote-read-replica \
>>>> --db-instance-identifier test-instance-repl
>>>>
>>>> Which breaks replication. You can't "demote".
>>
>>>
From | Date | Subject | |
---|---|---|---|
Next Message | Brett Bisesti | 2024-03-07 20:14:32 | Advanced DBA Training |
Previous Message | Keith | 2024-03-07 16:46:51 | Re: Regarding(Read Replica in RDS) |