From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: B Ganesh Kishan <bkishan@commvault.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Meera Nair <mnair@commvault.com>
Subject: Re: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
Date: Fri, 21 Jan 2022 10:20:46 -0500
Message-ID: <1183620.1642778446@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwZA1n-h40BCSFRoyrZ-_=+_LMZBSRoFOWVkKtv_8qR3jg@mail.gmail.com>
References: <17375-981fa49736cc1ae1@postgresql.org>
<SA1PR19MB5088B2372C402F08177D3C36B75B9@SA1PR19MB5088.namprd19.prod.outlook.com>
<CAKFQuwZA1n-h40BCSFRoyrZ-_=+_LMZBSRoFOWVkKtv_8qR3jg@mail.gmail.com>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Fri, Jan 21, 2022 at 4:20 AM B Ganesh Kishan <bkishan@commvault.com>
> wrote:
>> The problem is that we are providing a time target that Postgres does not
>> know how to reach. This is because there are no transactions in between the
>> backups.
> I don't quite follow the overall situation but given your observation and
> apparent acceptance of the pre-v13 behavior just don't specify a restore
> point and let WAL replay everything.
Yeah. If I'm understanding the situation, when you specify a target time
that is later than the last transaction available from WAL, older versions
silently assumed that stopping with the last available transaction is OK.
Newer ones complain because it's not clear whether that's OK --- in
particular, there's no good way to be sure that no WAL is missing.
On the whole I think that's a good change. I can sympathize with the
complaint that it creates additional complexity for restore scripts,
but I'm a little dubious that this is something you'd be wanting to
script anyway.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, bkishan@commvault.com, pgsql-bugs@lists.postgresql.org, mnair@commvault.com
Subject: Re: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
In-Reply-To: <1183620.1642778446@sss.pgh.pa.us>
* 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