From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PITR |
Date: | 2024-05-17 13:41:45 |
Message-ID: | 8fd671ff-52bc-8ecd-d4c5-130eb19cd31b@sqlexec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
To answer your question, logging DDL does not have ANYTHING to do with
PITR. So the answer is "NO, you cannot do PITR by just logging logging
DDL".
You have to use binary backups and continuous WAL logging to be able to
do PITR. There are many tools out there to do that. The best one in my
opinion is PGBackrest.
Regards,
Michael Vitale
Ron Johnson wrote on 5/17/2024 9:26 AM:
> On Fri, May 17, 2024 at 7:35 AM Rajesh Kumar
> <rajeshkumar(dot)dba09(at)gmail(dot)com <mailto:rajeshkumar(dot)dba09(at)gmail(dot)com>> wrote:
>
> Hi all,
>
>
> I want to verify one thing. If I am logging only ddl and if
> somebody update data incorrectly and if we don't know the time,
> can we do pitr or not?
>
>
> If your system is busy, then log_statement = 'mod' is going to
> generate a LOT of pg_log data.
>
Regards,
Michael Vitale
Michaeldba(at)sqlexec(dot)com <mailto:michaelvitale(at)sqlexec(dot)com>
703-600-9343
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar | 2024-05-17 13:47:26 | Re: PITR |
Previous Message | Ron Johnson | 2024-05-17 13:26:16 | Re: PITR |