On Monday, January 07, 2013 6:30 PM Simon Riggs wrote:
> On 7 January 2013 12:39, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> > So We can modify to change this in function LogStandbySnapshot as
> > 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
> > 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.
But isn't the functionality of LogStandbySnapshot() is to log "all running
xids" and "all current
AccessExclusiveLocks". For RunningTransactionLocks, WAL is avoided in
> If we skip the WAL record in the way you suggest, we'd be unable to
> start quickly in some cases.
If there are any operations happened which have generated WAL, then on next
checkpoint interval the checkpoint operation should happen.
Which cases will it not able to start quickly?
In response to
pgsql-hackers by date
|Next:||From: Greg Stark||Date: 2013-01-07 13:36:33|
|Subject: Re: Improve compression speeds in pg_lzcompress.c|
|Previous:||From: Simon Riggs||Date: 2013-01-07 13:00:03|
|Subject: Re: Extra XLOG in Checkpoint for StandbySnapshot|