Problems when a table grows beyond 65535 pointer pages [CORE4384] #4706
Submitted by: @ibprovider
The USHORT pp_sequence number wraps and it may lead to unexpected issues like an infinite loop inside extend_relation() or locate_space(). This issue manifests itself when a table (including garbage) gets bigger than 256GB (for 4KB page) ... 4TB (for 16KB page) and remains even after a garbage collection pass.
====== Test Details ======
There is no .fbt file for this ticket, but I've done such test and result was: table CAN be of such size that more than 64K PP will be related to it.
The text was updated successfully, but these errors were encountered:
Commented by: @pavel-zotov
I've done somewhat like test about ability to create and fill table with more than 65K pointer pages.
Environment: OS = Windows XP, FB = WI-T188.8.131.52543, SuperServer; database = page_4k, fw_OFF
DefaultDbCachePages = 64K
RemoteServicePort = 3333
MaxUnflushedWrites = -1
ExternalFileAccess = Restrict C:\1INSTALL\FBTEST
FileSystemCacheThreshold = 65536K
Modified by: @pavel-zotov
status: Resolved [ 5 ] => Resolved [ 5 ]
QA Status: Done successfully
Test Details: There is no .fbt file for this ticket, but I've done such test and result was: table CAN be of such size that more than 64K PP will be related to it.