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
Make the placement of BLOBs in same page with data or on separate page configurable [CORE2056] #2492
Comments
Modified by: Smirnoff Serg (wildsery)summary: Make the placement of BLOBs in same page witn data or on separate page configurable => Make the placement of BLOBs in same page with data or on separate page configurable |
Modified by: Smirnoff Serg (wildsery)description: Firebird core decide to keep BLOB on same page or on separate page for the only reason of the size of BLOB, omit the programmer's opinion on that issue. => Firebird core decide to keep BLOB on same page or on separate page for the only reason of the size of BLOB, omit the programmer's opinion on that issue. |
Commented by: Nikolay Ponomarenko (pnv82) But you can make separate table for those blobs... |
Commented by: Smirnoff Serg (wildsery) Yep. And TWO multimegabyte indices for control 1:1 referential integrity (see CORE651 for details). As addition for other excess actions... |
Commented by: Michiel Spoor (mdspoor) As I understand things, NOT having BLOB's on the same page as the regular datafields could significantly improve performance of queries. As I see it, it could be a *very* interesting feature, at a possibly very small cost. |
Commented by: @dyemanov Michiel, > As I understand things, NOT having BLOB's on the same page as the regular datafields True, but only fot the queries that don't read blobs. And it will decrease performance of the queries that read blobs along with other fields. |
Commented by: Michiel Spoor (mdspoor) Dmitry, >True, but only fot the queries that don't read blobs. And it will decrease performance of the queries that read blobs along with other fields. So it depends on the type of data in the blob and subsequently the way the data is retrieved by the application... |
Commented by: @hvlad ODS12 introduced two kinds of data pages - primary, where all primary record versions are stored, and secondary, where primary record versions are not stored (it contains backversions, fragments and blobs). Note, before ODS12 blob records could be stored at the same page as primary record version or at another page - it was not deterministic. |
Submitted by: Smirnoff Serg (wildsery)
Votes: 2
Firebird core decide to keep BLOB on same page or on separate page for the only reason of the size of BLOB, omit the programmer's opinion on that issue.
In sertain conditions (for ex. "million-record" tables with small-size BLOBs) there's necessarity to keep BLOB fields apart from data for faster data access.
I consider that this action will take much more data pages, but I insist that in some cases faster data access in price of storage consumption is acceptable.
The text was updated successfully, but these errors were encountered: