Greetings,
* cen (imba...@gmail.com) wrote:
> Seems like a lot of manual work to me, to automate it I'd basically
> have to diff both directories and then copy only the newest
> differences over to the recovery. So far I was unable to find a
> supersecret git repo with bash scripts accomplishing
That is really unfortunate. It seems it would be a nice feature for
pg_basebackup to simply create a .metadata file in basebackup output
directory or something along those lines.
Non tarballed/compressed basebackup is fine since I can read the label,
but most people probably want to always
On Thu, Jul 13, 2017 at 10:30 AM, cen wrote:
> Given a basebackup base.tar.gz and an archive of WAL files, is there any way
> to find out which .backup WAL file is associated with the basebackup from
> command line?
Not from what Postgres ships directly. Without any custom
Hi
Given a basebackup base.tar.gz and an archive of WAL files, is there any
way to find out which .backup WAL file is associated with the basebackup
from command line?
My use case is for a retention policy bash script which:
-deletes all basebackups older than X days
-runs