[MDEV-6915] Allow packed keys and packed values of non-sorted fields in the sort buffer Created: 2014-10-23  Updated: 2020-03-26  Resolved: 2020-03-26

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Fix Version/s: N/A

Type: Task Priority: Critical
Reporter: Igor Babaev Assignee: Varun Gupta (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-6529 optimize VARCHAR temp storage during ... Confirmed
PartOf
includes MDEV-21263 Allow packed values of non-sorted fie... Closed
includes MDEV-21580 Allow packed sort keys in sort buffer Closed
includes MDEV-21772 Testing for packed sort keys and pack... Closed
Relates
relates to MDEV-21838 Add information about packed addon fi... Closed
relates to MDEV-21829 Use packed sort keys in Unique objects In Review
relates to MDEV-21922 Allow packing addon fields even if th... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MDEV-21263 Allow packed values of non-sorted fie... Technical task Closed Varun Gupta  
MDEV-21580 Allow packed sort keys in sort buffer Technical task Closed Varun Gupta  

 Description   

This task will allow to have packed keys and packed values of non-sorted fields in the sort buffer.
It will incorporate the code of wl 1509 from mysql-5.7 that implemented packed values of non-sorted fields in the sort buffer.
Packed keys in sort buffer will help greatly to resolve the problem of
mdev-6529.



 Comments   
Comment by Sergei Petrunia [ 2015-11-27 ]

Added estimate as discussed

Comment by Varun Gupta (Inactive) [ 2019-12-02 ]

Patch
http://lists.askmonty.org/pipermail/commits/2019-December/014080.html

Comment by Varun Gupta (Inactive) [ 2020-01-02 ]

A big test case is required to test the feature.
Here is the patch for it
http://lists.askmonty.org/pipermail/commits/2020-January/014120.html

Comment by Igor Babaev [ 2020-01-29 ]

Review is needed only for subtasks

Comment by Varun Gupta (Inactive) [ 2020-03-26 ]

The task is completed by the sub tasks MDEV-21263 and MDEV-21580

Generated at Thu Feb 08 07:15:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.