From: | Rui DeSousa <rui(at)crazybean(dot)net> |
---|---|
To: | Licio Matos <licio(dot)matos(at)gmail(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Backup From HotStandby |
Date: | 2019-08-28 20:38:47 |
Message-ID: | 4BB72752-69DB-4ADA-A92F-4B7EE238A3EA@crazybean.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Aug 28, 2019, at 4:11 PM, Licio Matos <licio(dot)matos(at)gmail(dot)com> wrote:
>
> @Rui DeSousa <mailto:rui(at)crazybean(dot)net>
>
> I am running this on the primary, the question is if i can run this same script on the replica.
>
You can based on what you told me about the snapshot; however, the pg_start_backup() command will fail.
Note: What you are doing today most would consider it a “proper” online backup; when you start running the script on the replica then you will end up with a “crashed” backup. The “crashed” backup only works as you can guarantee a point in time atomic view of all the data files using a single atomic snapshot.
You need to remove the pg_start_backup() and pg_stop_backup() commands from the script. The backup should occur faster as it is no longer waiting on pg_start_backup() to issue checkpoint; however, that also means that recovery times increase for the same reason.
From | Date | Subject | |
---|---|---|---|
Next Message | Licio Matos | 2019-08-28 20:59:11 | Re: Backup From HotStandby |
Previous Message | Licio Matos | 2019-08-28 20:11:23 | Re: Backup From HotStandby |