Re: Extra XLOG in Checkpoint for StandbySnapshot
От | Simon Riggs |
---|---|
Тема | Re: Extra XLOG in Checkpoint for StandbySnapshot |
Дата | |
Msg-id | CA+U5nMJLn1S72bC+B6B7fNV0a5=g+Cjj0g5AOCjnGoCBBBgLAA@mail.gmail.com обсуждение исходный текст |
Ответ на | Extra XLOG in Checkpoint for StandbySnapshot (Amit Kapila <amit.kapila@huawei.com>) |
Ответы |
Re: Extra XLOG in Checkpoint for StandbySnapshot
|
Список | 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 по дате отправления: