-
-
Notifications
You must be signed in to change notification settings - Fork 241
Problems when a table grows beyond 65535 pointer pages [CORE4384] #4706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Modified by: @dyemanovreporter: Dmitry Yemanov [ dimitr ] => Kovalenko Dmitry [ _dima_k_ ] assignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovFix Version: 3.0 Beta 2 [ 10586 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.4 [ 10585 ] |
Commented by: @pavel-zotov http://svn.code.sf.net/p/firebird/code/firebird/trunk/ChangeLog: 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-T6.3.0.31543, SuperServer; database = page_4k, fw_OFF firebird.conf:DefaultDbCachePages = 64K RemoteServicePort = 3333 MaxUnflushedWrites = -1 ExternalFileAccess = Restrict C:\1INSTALL\FBTEST FileSystemCacheThreshold = 65536K
|
Modified by: @pavel-zotovAttachment: miscelan-logs.zip [ 12670 ] Attachment: inserts-batch-and-sql.zip [ 12671 ] |
Modified by: @pavel-zotovAttachment: fill_huge_table_log_until_count_3e9_fw-ON.zip [ 12674 ] |
Modified by: @dyemanovAttachment: fill_huge_table_log_until_count_3e9_fw-ON.zip [ 12674 ] => |
Modified by: @pavel-zotovstatus: 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. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @ibprovider
Attachments:
miscelan-logs.zip
inserts-batch-and-sql.zip
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.
Commits: 1655ba4 bd3ce4e FirebirdSQL/fbt-repository@ec2c79f FirebirdSQL/fbt-repository@3d5e270
====== 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: