public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Running rsync backups in pg15
Date: Fri, 8 Nov 2024 10:32:34 -0500
Message-ID: <CANzqJaBZ+j2o8jQ8Hs63AQbAZfiFcyApa5d212A1LNkagqyrGQ@mail.gmail.com> (raw)
In-Reply-To: <DM8PR09MB6677F19E2DDD6E18A4FDE2D6B85D2@DM8PR09MB6677.namprd09.prod.outlook.com>
References: <CANzqJaCr-id_4YotukPeH=rHCELS58Z63FoEbkNFBSqzjGMueQ@mail.gmail.com>
<01000193082d1077-34d9461d-49e4-44ef-b83a-0201df4fc0ba-000000@email.amazonses.com>
<DM8PR09MB6677705AE81436745B4487F6B85C2@DM8PR09MB6677.namprd09.prod.outlook.com>
<CANzqJaA02zeZTUB=uFPfxgJ+=NUUy1cQP3E0=3u0ssHdL6qkMA@mail.gmail.com>
<DM8PR09MB6677F19E2DDD6E18A4FDE2D6B85D2@DM8PR09MB6677.namprd09.prod.outlook.com>
According to
https://www.postgresql.org/docs/14/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
Section 26.3.3.2, SELECT pg_backup_start('label') is how you start
Exclusive Low Level backups.
https://www.postgresql.org/docs/release/15.0/ says that this has been
removed.
On Fri, Nov 8, 2024 at 10:07 AM Murthy Nunna <[email protected]> wrote:
> Yes. We already have streaming replication. But we still rely on rsync
> backups for PITR. We keep two copies of rsync backups. The oldest full
> rsync is 7 days. We save all WALs for 8 days. We do not want to change this
> scheme. There are some bells and whistles during rsync to monitor the
> backup. With the introduction of new requirement ( need to run
> pg_backup_start/stop in same connection) we end up rewriting our backup
> scripts.
>
>
>
> As noted earlier, I did a crash test in pg14 (which uses old functions
> pg_start_backup/stop in separate connections) but I did not encounter any
> issue like lingering backup_label file that prevents cluster restart etc.
> What I noticed is pg14 is nicely renaming the backup_label file before
> restarting the cluster.
>
>
>
> Please (pretty please) somebody tell me (via a URL that explains is good
> enough) what problem is solved by introducing the new restriction of having
> to run pg_backup_start/stop in same connection. I am pretty sure I am
> missing the point… May be I should run the crash test in a different way to
> reproduce the issue.
>
>
>
>
>
> *From:* Ron Johnson <[email protected]>
> *Sent:* Friday, November 8, 2024 8:09 AM
> *To:* pgsql-admin <[email protected]>
> *Subject:* Re: Running rsync backups in pg15
>
>
>
> That looks a whole lot like the results you get from async Streaming
> Replication.
>
>
>
> Which is, of course, a DR solution, NOT a backup solution.
>
>
>
> --
>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (24+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Running rsync backups in pg15
In-Reply-To: <CANzqJaBZ+j2o8jQ8Hs63AQbAZfiFcyApa5d212A1LNkagqyrGQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox