From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | bharath(dot)rupireddyforpostgres(at)gmail(dot)com |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Missing log message in recoveryStopsAfter() for RECOVERY_TARGET_TIME recovery target type |
Date: | 2021-10-14 01:35:00 |
Message-ID: | 20211014.103500.372332111600744878.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Wed, 13 Oct 2021 19:56:17 +0530, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote in
> Hi,
>
> I see that the recoveryStopsAfter() doesn't have any "recovery
> stopping after XXXX" sort of log for RECOVERY_TARGET_TIME recovery
> target type. It has similar logs for other recoveryTarget types
> though. Is there any specific reason for not having it?
>
> I see that we have "starting point-in-time recovery to XXXX" sorts of
> logs for all the recovery target types and also recoveryStopsBefore()
> has a log (by setting stopsHere) for RECOVERY_TARGET_TIME.
So you should have seen the following comment there.
> /*
> * There can be many transactions that share the same commit time, so
> * we stop after the last one, if we are inclusive, or stop at the
> * first one if we are exclusive
> */
Since both inclusive and exclusive cases are processed in
recoveryStopsBefore(), recoveryStopsAfter() has nothing to do for the
target type.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-10-14 01:39:07 | Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns |
Previous Message | Kyotaro Horiguchi | 2021-10-14 01:09:56 | Re: Allow escape in application_name |