Skip to content

Fix for #8105: Master database could miss replication segments on Windows Classic Server#8106

Merged
hvlad merged 3 commits intov4.0-releasefrom
work/gh-8105
May 8, 2024
Merged

Fix for #8105: Master database could miss replication segments on Windows Classic Server#8106
hvlad merged 3 commits intov4.0-releasefrom
work/gh-8105

Conversation

@hvlad
Copy link
Copy Markdown
Member

@hvlad hvlad commented May 7, 2024

The main problem is that on Windows it is not allowed to rename open files with mapped memory section.
rename() for such file always set errno to EACCES, GetLastError() returns ERROR_SHARING_VIOLATION.

hvlad added 2 commits May 7, 2024 13:44
@hvlad hvlad self-assigned this May 7, 2024
@hvlad hvlad requested a review from dyemanov May 7, 2024 10:49
@hvlad hvlad linked an issue May 7, 2024 that may be closed by this pull request
Comment thread src/jrd/replication/ChangeLog.cpp
Comment thread src/jrd/replication/ChangeLog.cpp Outdated
Removed not used g_dummyHeader.
@hvlad hvlad merged commit 2d9e479 into v4.0-release May 8, 2024
hvlad added a commit that referenced this pull request May 8, 2024
Fix for #8105:  Master database could miss replication segments on Windows Classic Server
hvlad added a commit that referenced this pull request May 8, 2024
Fix for #8105:  Master database could miss replication segments on Windows Classic Server
@hvlad hvlad deleted the work/gh-8105 branch May 8, 2024 14:18
dyemanov pushed a commit that referenced this pull request Nov 16, 2024
Fix for #8105:  Master database could miss replication segments on Windows Classic Server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Master database could miss replication segments on Windows Classic Server

2 participants