From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: PITR
Date: Fri, 17 May 2024 09:41:45 -0400
Message-ID: <8fd671ff-52bc-8ecd-d4c5-130eb19cd31b@sqlexec.com> (raw)
In-Reply-To: <CANzqJaA65rqOEBRt+jUdF2nGmMOyU0nhA9TjpiPi9NqxcX1tFw@mail.gmail.com>
References: <CAJk5AtYCh7fWShBqo6L3WQjAm2-PEqpYEZ5D=1Vp_xAympU=tw@mail.gmail.com>
<CANzqJaA65rqOEBRt+jUdF2nGmMOyU0nhA9TjpiPi9NqxcX1tFw@mail.gmail.com>
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.dba09@gmail.com <mailto:rajeshkumar.dba09@gmail.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@sqlexec.com <mailto:michaelvitale@sqlexec.com>
703-600-9343
Attachments:
[image/jpeg] pgadvanced3.jpg (20.6K, ../8fd671ff-52bc-8ecd-d4c5-130eb19cd31b@sqlexec.com/3-pgadvanced3.jpg)
download | view image
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: MichaelDBA@sqlexec.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: PITR
In-Reply-To: <8fd671ff-52bc-8ecd-d4c5-130eb19cd31b@sqlexec.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox