[BUGS] BUG #14803: use receiverPtr as the endptr to call KeepLogSeg(endptr,&_logSegNo) in CreateRestartPoint - Mailing list pgsql-bugs

From bret.shao@outlook.com
Subject [BUGS] BUG #14803: use receiverPtr as the endptr to call KeepLogSeg(endptr,&_logSegNo) in CreateRestartPoint
Date
Msg-id 20170907051056.25634.72330@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14803: use receiverPtr as the endptr to callKeepLogSeg(endptr, &_logSegNo) in CreateRestartPoint
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14803
Logged by:          bret shao
Email address:      bret.shao@outlook.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);




--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: vinod.t.v@outlook.com
Date:
Subject: [BUGS] BUG #14802: Installation failed for french password Télécharger
Next
From: Francisco Olarte
Date:
Subject: Re: [BUGS] BUG #14800: substring produces different results withsimilar types