| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Something else about Redo Logs disappearing |
| Date: | 2020-06-15 13:19:29 |
| Message-ID: | ec8d3b4c811519aa377c94f83450f046a62fd38c.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2020-06-15 at 14:50 +0200, Peter wrote:
> ! An example:
> !
> ! - Backup #1 calls "pgpre.sh"
> ! - Backup #1 starts copying files
> ! - Backup #2 calls "pgpre.sh".
> ! This will cancel the first backup.
> ! - Backup #1 completes copying files.
> ! - Backup #1 calls "pgpost.sh".
> ! It will receive an error.
> ! So it has to invalidate the backup.
> ! - Backup #2 completes copying files.
> ! - Backup #2 calls "pgpost.sh".
> ! It gets a "backup_label" file and completes the backup.
>
> That's not true.
Ah, yes, you are right.
It's a while since I wrote these scripts.
Since "pgpre.sh" and "pgpost.sh" are independent, there
is no way to tell which of them belongs to which other.
So calling "pgpost.sh" indeed ends the most recently started
backup and returns "backup_label" accordingly.
That means: the caller of the scripts has to make sure
not to start a second backup while the first one is running.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sonam Sharma | 2020-06-15 13:21:14 | Replication error |
| Previous Message | Peter | 2020-06-15 12:50:22 | Re: Something else about Redo Logs disappearing |