Re: [HACKERS] What does it mean by XLOG_BACKUP_RECORD?
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] What does it mean by XLOG_BACKUP_RECORD? |
Дата | |
Msg-id | CAB7nPqT+X6ExvQ-nYiYH2vQRV+M65JXX6eJV4jhmg2+J3updHw@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] What does it mean by XLOG_BACKUP_RECORD? (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: [HACKERS] What does it mean by XLOG_BACKUP_RECORD?
|
Список | pgsql-hackers |
On Thu, Jun 29, 2017 at 10:28 AM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > While reading source codes I found the following comment in xlog.c. > > /* > * Have we passed our safe starting point? Note that minRecoveryPoint is > * known to be incorrectly set if ControlFile->backupEndRequired, until > * the XLOG_BACKUP_RECORD arrives to advise us of the correct > * minRecoveryPoint. All we know prior to that is that we're not > * consistent yet. > */ > if (!reachedConsistency && !ControlFile->backupEndRequired && > minRecoveryPoint <= lastReplayedEndRecPtr && > XLogRecPtrIsInvalid(ControlFile->backupStartPoint)) > > What does XLOG_BACKUP_RECORED means by? I could not find such XLOG info value. > Does it mean XLOG_BACKUP_END? This comment is a thinko, it refers to XLOG_BACKUP_END. This comment block could be reworded a bit, it looks cleaner to me to say "ControlFile->backupEndRequired is false" instead of just referring to the variable itself. Worse, the current comment implies that minRecoveryPoint is incorrectly set if it is true. Bleh. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: