Re: Extra XLOG in Checkpoint for StandbySnapshot - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Extra XLOG in Checkpoint for StandbySnapshot
Date
Msg-id CA+U5nMJLn1S72bC+B6B7fNV0a5=g+Cjj0g5AOCjnGoCBBBgLAA@mail.gmail.com
Whole thread Raw
In response to Extra XLOG in Checkpoint for StandbySnapshot  (Amit Kapila <amit.kapila@huawei.com>)
Responses Re: Extra XLOG in Checkpoint for StandbySnapshot
List pgsql-hackers
On 7 January 2013 12:39, Amit Kapila <amit.kapila@huawei.com> wrote:

> So We can modify to change this in function LogStandbySnapshot as below:
>                 running = GetRunningTransactionData();
>                 if (running->xcnt > 0)
>                         LogCurrentRunningXacts(running);
>
> So this check will make sure that if there is no operation happening i.e. no
> new running transaction, then no need to log running transaction snapshot
> and hence further checkpoint operations will be skipped.
>
> Let me know if I am missing something?

It's not the same test. The fact that nothing is running at that
moment is not the same thing as saying nothing at all has run since
last checkpoint.

If we skip the WAL record in the way you suggest, we'd be unable to
start quickly in some cases.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Extra XLOG in Checkpoint for StandbySnapshot
Next
From: "孟庆钟"
Date:
Subject: A very small typo in the comment