Problems when a table grows beyond 65535 pointer pages [CORE4384] #4706
Labels
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.1.4
affect-version: 2.1.5 Update 1
affect-version: 2.1.5
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2 Update 1
affect-version: 2.5.2
affect-version: 3.0 Alpha 1
affect-version: 3.0 Alpha 2
component: engine
fix-version: 2.5.4
fix-version: 3.0 Beta 2
priority: major
qa: done successfully
type: bug
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: