public inbox for [email protected]  
help / color / mirror / Atom feed
Re: Review my steps for rollback to restore point
2+ messages / 2 participants
[nested] [flat]

* Re: Review my steps for rollback to restore point
@ 2025-03-04 15:37  Ron Johnson <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Ron Johnson @ 2025-03-04 15:37 UTC (permalink / raw)
  To: pgsql-general

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 <[email protected]>
wrote:

> 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 <[email protected]>
> 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 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_point()
>> > 3-  executed some DDL statement (CREATE VIEW,ADD INDEX,DROP INDEX)
>> > 4-  Perform rollback using restore point
>> >  To rollback, you must stop PostgreSQL, restore the last full backup,
>> and apply
>> >  WAL files until the restore point:
>> > 1. Stop PostgreSQL Service
>> > 2. Restore from Full Backup (Using pg_basebackup)
>>
> [snip]
-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Review my steps for rollback to restore point
@ 2025-03-04 15:42  chandan Kumar <[email protected]>
  parent: Ron Johnson <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: chandan Kumar @ 2025-03-04 15:42 UTC (permalink / raw)
  To: Ron Johnson <[email protected]>; +Cc: pgsql-general

Thank you !

On Tue, Mar 4, 2025 at 9:08 PM Ron Johnson <[email protected]> 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 *hot standby*, not backups.
>
>
> On Tue, Mar 4, 2025 at 10:00 AM chandan Kumar <[email protected]>
> wrote:
>
>> 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 <[email protected]>
>> 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 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_point()
>>> > 3-  executed some DDL statement (CREATE VIEW,ADD INDEX,DROP INDEX)
>>> > 4-  Perform rollback using restore point
>>> >  To rollback, you must stop PostgreSQL, restore the last full backup,
>>> and apply
>>> >  WAL files until the restore point:
>>> > 1. Stop PostgreSQL Service
>>> > 2. Restore from Full Backup (Using pg_basebackup)
>>>
>> [snip]
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>


-- 
*With warm regards*
*     Chandan*


^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2025-03-04 15:42 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-03-04 15:37 Re: Review my steps for rollback to restore point Ron Johnson <[email protected]>
2025-03-04 15:42 ` chandan Kumar <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox