From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | chandan Kumar <chandan(dot)issyoga(at)gmail(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Review my steps for rollback to restore point |
Date: | 2025-03-04 15:38:07 |
Message-ID: | CAKFQuwbzEDV2e4yfSpr8SkLyxEmAk=WPn3uo3C2q+1xR5VymVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tuesday, March 4, 2025, chandan Kumar <chandan(dot)issyoga(at)gmail(dot)com> 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 without PITR in streaming
> replication
>
PostgreSQL doesn’t have a concept of “revert”.
PITR just deals with raw bytes on disk for an entire cluster. If a new
file appears in the WAL that file is created. That file can be a directory
for a database.
You cannot mix physical and logical images of the database so applying WAL
on top of pg_restore is technically invalid - but it does effective convey
the idea. It’s like saying pg_dump and pg_basebackup are similar. Sure,
in some ways that is true - but the logical vs. physical distinction cannot
be ignored fully.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | chandan Kumar | 2025-03-04 15:42:54 | Re: Review my steps for rollback to restore point |
Previous Message | Ron Johnson | 2025-03-04 15:37:53 | Re: Review my steps for rollback to restore point |