Message-ID: <e8bc180a-17c2-4d1a-8b00-5fe5eb7e42d2@crashdump.ch>
Date: Tue, 1 Jul 2025 06:35:37 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Simulate a PITR in postgresql 16
To: pgsql-general@lists.postgresql.org
References: <CAB_Px=yO5y-6NcZjyDxLUGb4m6VX=-UXhSiuB7eLXp10eRfdQw@mail.gmail.com>
 <CANzqJaBNufPWAhkNXHBHy2hySOKhPPcYy1sZi=ZHFp-D9j-o5g@mail.gmail.com>
From: raphi <raphi@crashdump.ch>
In-Reply-To: <CANzqJaBNufPWAhkNXHBHy2hySOKhPPcYy1sZi=ZHFp-D9j-o5g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/e8bc180a-17c2-4d1a-8b00-5fe5eb7e42d2%40crashdump.ch>
Precedence: bulk


Am 30.06.2025 um 21:45 schrieb Ron Johnson:
> Using PgBackRest might be more convenient, since it handles everything 
> you need, is multithreaded, never removes too many wal files, 
> compresses files if you want and also encrypts them if you want.
>
I agree, with pgBackRest it's basically: pgbackrest --stanza=demo 
--delta --type=time "--target=2025-05-05 15:37:03.157376+00" 
--target-action=promote restore

and you are done. It will also restore configure files and you can also 
selectively restore only one DB in the cluster if you want to speed up 
things. Works very well with S3 too and is very easy to integrate in an 
ansible playbook to have a generic way to do PITRs.

Check out the official user guide: https://pgbackrest.org/user-guide.html

have fun
raphi