BUG #14803: use receiverPtr as the endptr to call KeepLogSeg(endptr, &_logSegNo) in CreateRestartPoint

From: bret(dot)shao(at)outlook(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Cc: bret(dot)shao(at)outlook(dot)com
Subject: BUG #14803: use receiverPtr as the endptr to call KeepLogSeg(endptr, &_logSegNo) in CreateRestartPoint
Date: 2017-09-07 05:10:56
Message-ID: 20170907051056.25634.72330@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14803
Logged by: bret shao
Email address: bret(dot)shao(at)outlook(dot)com
PostgreSQL version: 9.5.7
Operating system: ubantu
Description:

when call KeepLogSeg to get the oldest xlog file in function
CreateRestartPoint,
I think the endptr shoule be the repalyPtr not the later one of receiverPtr
and replayPtr.
endptr = (receivePtr < replayPtr) ? replayPtr : receivePtr;

Because that if the endptr is the receiverPtr, it means that may be the xlog
file that is being redo will be dropped.

if the file which is being needed in recover redo work is dropped then the
server will down.

i'm not very clear why use receiverPtr as the endptr to call
KeepLogSeg(endptr, &_logSegNo);

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Francisco Olarte 2017-09-07 08:09:34 Re: BUG #14800: substring produces different results with similar types
Previous Message vinod.t.v 2017-09-07 04:59:10 BUG #14802: Installation failed for french password Télécharger