Re: Review my steps for rollback to restore point

2025-03-07 Thread Greg Sabino Mullane
On Thu, Mar 6, 2025 at 6:49 AM chandan Kumar wrote: > need any correction or advise. > Honestly, this all seems overly complex and fragile. I'm not sure what the overall goal is, but if it's to have a general PITR solution, use pgBackRest. If it's just to have a fall back method for a particular

Re: Review my steps for rollback to restore point

2025-03-06 Thread chandan Kumar
Dear Team, Thank you for all the responses I have received in this matter. I would like to send my final steps that I am going to follow during PITR. kindly take some out to see if these steps are correct or need any correction or advise. *Performing Database rollback using PITR* *Steps: * *Pre

Re: Review my steps for rollback to restore point

2025-03-04 Thread chandan Kumar
Hi David, You catched my word "revert". Thats so encouraging to see how this community helps. Your answer has cleared my 99% doubt. Thanks again. I wish I also contribute one day . Have a good time! On Tue, Mar 4, 2025 at 9:08 PM David G. Johnston wrote: > On Tuesday, March 4, 2025, chandan Kum

Re: Review my steps for rollback to restore point

2025-03-04 Thread chandan Kumar
Thank you ! On Tue, Mar 4, 2025 at 9:08 PM Ron Johnson wrote: > Chandran, > > >1. For PITR, you should use a tool like PgBackRest. It handles all >$PGDATA and WAL archiving. It's multithreaded, too, >2. pg_restore is just for logical backups. >3. Streaming Replication is for *h

Re: Review my steps for rollback to restore point

2025-03-04 Thread David G. Johnston
On Tuesday, March 4, 2025, chandan Kumar wrote: > Thank you for your time and clarification. > Does PITR recreate database internally ? can i say it is not the same as > pg_restore or it is same as pg_restore plus applying WAL on top of it. I > am asking because can we revern DDL operations wi

Re: Review my steps for rollback to restore point

2025-03-04 Thread Ron Johnson
Chandran, 1. For PITR, you should use a tool like PgBackRest. It handles all $PGDATA and WAL archiving. It's multithreaded, too, 2. pg_restore is just for logical backups. 3. Streaming Replication is for *hot standby*, not backups. On Tue, Mar 4, 2025 at 10:00 AM chandan Kumar wr

Re: Review my steps for rollback to restore point

2025-03-04 Thread chandan Kumar
Thank you for your time and clarification. Does PITR recreate database internally ? can i say it is not the same as pg_restore or it is same as pg_restore plus applying WAL on top of it. I am asking because can we revern DDL operations without PITR in streaming replication On Tue, Mar 4, 2025 a

Re: Review my steps for rollback to restore point

2025-03-04 Thread David G. Johnston
On Tuesday, March 4, 2025, chandan Kumar wrote: > Thank you for your answer. I want to clarify one more doubt. Can PITR be > achieved without applying Base Backup > The point-in-time you choose must be in the future relative to whatever data files you are applying WAL on top of. That is only

Re: Review my steps for rollback to restore point

2025-03-04 Thread chandan Kumar
Thank you for your answer. I want to clarify one more doubt. Can PITR be achieved without applying Base Backup On Tue, Mar 4, 2025 at 3:12 PM Laurenz Albe wrote: > On Tue, 2025-03-04 at 14:26 +0530, chandan Kumar wrote: > > Hello, > > I hope you are doing fine. I need your expertise on below

Re: Review my steps for rollback to restore point

2025-03-04 Thread Laurenz Albe
On Tue, 2025-03-04 at 14:26 +0530, chandan Kumar wrote: > Hello, >  I hope you are doing fine. I need your expertise on below case study. > My current production environment is 2 node streaming replication hosted on > Ubuntu VM 's on Azure. I have performed below steps on primary database. > 1- Tak

Review my steps for rollback to restore point

2025-03-04 Thread chandan Kumar
Hello, I hope you are doing fine. I need your expertise on below case study. My current production environment is 2 node streaming replication hosted on Ubuntu VM 's on Azure. I have performed below steps on primary database. 1- Take Base backup 2- Create a restore point using pg_create_restore_p