public inbox for pgsql-novice@postgresql.org
help / color / mirror / Atom feedFrom: Subramanian,Ramachandran <ramachandran.subramanian@alte-leipziger.de>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-novice@lists.postgresql.org <pgsql-novice@lists.postgresql.org>
Subject: AW: Very basic question about Archive logs
Date: Thu, 26 Mar 2026 12:38:56 +0000
Message-ID: <5604c5c610e44a0d97daceaf5f1ae01f@alte-leipziger.de> (raw)
In-Reply-To: <CAKFQuwZwA=sq7xeLV032QJCzZ99NQnq8SNg4a6Y_hBxN_D=PmA@mail.gmail.com>
References: <dee8d2457c034cddb7ab7021e1caf3f7@alte-leipziger.de>
<CAKFQuwZwA=sq7xeLV032QJCzZ99NQnq8SNg4a6Y_hBxN_D=PmA@mail.gmail.com>
Oh… Thank you for your reply.
so there is ONLY roll forward !!
So If I have to go to any time backwards from NOW , I WILL DEFINITELY need a backup older than NOW and all the Logs Active/Archive inbetween.
Just a theoretical question to better my understanding. If I take a backup on Monday at 0100 Hours and never make any further Backups but hold on to all the Logs ( Active and Archive),
I could theoretically go to any PIT between Monday 0100 Hours and NOW?
If I apply the base backup from Monday 0100 , how does Postgres know which Archive Logs need to be applied from it’s current state to get to the PIT. Obviously when the basebackup was taken, the now needed logs did not exist. So this information cannot have been recorded during the backup.
There is no rolling back. You deploy the base backup first to 0100 Monday, then it would apply the WAL up to the target time.
David J.
Freundliche Grüße
i. A. Ramachandran Subramanian
Zentralbereich Informationstechnologie
Alte Leipziger Lebensversicherung a.G.
Hallesche Krankenversicherung a.G.
Alte Leipziger Lebensversicherung a.G., Alte Leipziger-Platz 1, 61440 Oberursel
Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek
Sitz Oberursel (Taunus) · Rechtsform VVaG · Amtsgericht Bad Homburg v. d. H. HRB 1583 · USt.-IdNr. DE 114106814
Hallesche Krankenversicherung a.G., Löffelstraße 34-38, 70597 Stuttgart
Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape,
Wiltrud Pekarek, Udo Wilcsek
Sitz Stuttgart · Rechtsform VVaG · Amtsgericht Stuttgart HRB 2686 · USt.-IdNr. DE 147802285
Beiträge zu privaten Kranken- und Pflegekrankenversicherungen unterliegen nicht der Versicherungsteuer (§ 4 Nr. 5 VersStG) · Versicherungsleistungen sowie Umsätze aus Versicherungsvertreter-/Maklertätigkeiten sind umsatzsteuerfrei
Die Pflichtangaben der ALH Gruppe gemäß § 35a GmbHG bzw. § 80 AktG finden Sie hier: https://www.alte-leipziger.de/impressum
______________________
ALH Gruppe
Alte Leipziger-Platz 1, 61440 Oberursel
Tel.: +49 (6171) 66-4882
Fax: +49 (6171) 66-800-4882
E-Mail: ramachandran.subramanian@alte-leipziger.de
www.alte-leipziger.de
www.hallesche.de
reply
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-novice@postgresql.org
Cc: ramachandran.subramanian@alte-leipziger.de, david.g.johnston@gmail.com, pgsql-novice@lists.postgresql.org
Subject: Re: AW: Very basic question about Archive logs
In-Reply-To: <5604c5c610e44a0d97daceaf5f1ae01f@alte-leipziger.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox