Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-21 Thread Jeremy Finzel
> > I find this to be unactionably vague. What does it mean to claim "an > LSN is visible"? An LSN might not even point to a WAL record, or it > might point to one that has nontransactional effects. Moreover, any > behavior of this sort would destroy what I regard as a bedrock property > of

Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-21 Thread Tom Lane
Jeremy Finzel writes: >> I'd be in favor of that for recovery_target_xid, but I'm not at all >> convinced about changing the behavior for a target LSN. The fact that >> the target is a subcommit seems irrelevant when you specify by LSN. > For this use case, my goal is simply to be able to

Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-21 Thread Jeremy Finzel
> > It would seem like what you're asking for is to continue until the commit > of the parent transaction, not just the next commit after the subcommit. > Otherwise (if that's an unrelated xact) the subxact would still not be > committed, so that you might as well have stopped short of it. >

Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-20 Thread Tom Lane
Jeremy Finzel writes: > A related problem kind of demonstrates the same odd behavior. If you put > in recovery_target_xid to a subtransaction_id, it just skips it and > continues recovering, which really seems to be undesirable behavior. It > would be nice if that also could roll up to the next

Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-20 Thread Jeremy Finzel
> > If recovery_target_inclusive were able to take the third value > "xact", is it exactly what you want? > > And is it acceptable? > Yes, that would be exactly what I would want. It would work to have a 3rd value for recovery_target_inclusive, although perhaps it's debatable that instead, it

Re: Automated way to find actual COMMIT LSN of subxact LSN

2019-03-19 Thread Kyotaro HORIGUCHI
At Tue, 19 Mar 2019 12:16:34 -0500, Jeremy Finzel wrote in > I want to build automation to recover a database to a specific LSN > *inclusive*, even if that LSN is from a subtransaction. The problem I am > facing is that I know what specific LSN wrote a row on a remote system, but > if I create

Automated way to find actual COMMIT LSN of subxact LSN

2019-03-19 Thread Jeremy Finzel
I want to build automation to recover a database to a specific LSN *inclusive*, even if that LSN is from a subtransaction. The problem I am facing is that I know what specific LSN wrote a row on a remote system, but if I create a recovery.conf file with: recovery_target_lsn = '95F/BBA36DF8' and