Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Release notes for Percona Server 5.5.45-37.4 (5.6) #137

Merged
merged 2 commits into from
Sep 2, 2015
Merged

Release notes for Percona Server 5.5.45-37.4 (5.6) #137

merged 2 commits into from
Sep 2, 2015

Conversation

hrvojem
Copy link
Member

@hrvojem hrvojem commented Sep 2, 2015

Merge branch '5.5-ps-rn-5.5.45-37.4' into 5.6-ps-rn-5.5.45-37.4
Contains fixes for: Bug #1485770, DOC-154, DOC-157, DOC-158, DOC-160,
DOC-159, and DOC-165

@hrvojem
Release notes for Percona Server 5.5.45-37.4 (5.5)
59dc74e 
Contains fixes for: Bug #1485770, DOC-154, DOC-157, DOC-158, DOC-160
@hrvojem
Release notes for Percona Server 5.5.45-37.4 (5.6)
acd671e 
Merge branch '5.5-ps-rn-5.5.45-37.4' into 5.6-ps-rn-5.5.45-37.4
Contains fixes for: Bug #1485770, DOC-154, DOC-157, DOC-158, DOC-160,
DOC-159, and DOC-165
hrvojem added a commit that referenced this pull request Sep 2, 2015
@hrvojem
Merge pull request #137 from hrvojem/5.6-ps-rn-5.5.45-37.4
cbb583d 
Release notes for Percona Server 5.5.45-37.4 (5.6)
@hrvojem hrvojem merged commit cbb583d into percona:5.6 Sep 2, 2015
@hrvojem hrvojem deleted the 5.6-ps-rn-5.5.45-37.4 branch September 2, 2015 13:37
george-lorch pushed a commit to george-lorch/percona-server that referenced this pull request May 7, 2016
@yoshinorim
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
e403bd6 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Test Plan:
New test case truncate_table3 and shared with drop_table3.
Note that truncate_table2 does not exist, but I chose truncate_table3 as
a name since it relies on drop_table3.

Reviewers: jkedgar, hermanlee4, spetrunia

Reviewed By: spetrunia

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D53031
george-lorch pushed a commit to george-lorch/percona-server that referenced this pull request May 7, 2016
@yoshinorim
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
ddf08d9 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Test Plan:
New test case truncate_table3 and shared with drop_table3.
Note that truncate_table2 does not exist, but I chose truncate_table3 as
a name since it relies on drop_table3.

Reviewers: jkedgar, hermanlee4, spetrunia

Reviewed By: spetrunia

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D53031
george-lorch pushed a commit to george-lorch/percona-server that referenced this pull request May 9, 2016
@yoshinorim
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
f4e6ff7 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Test Plan:
New test case truncate_table3 and shared with drop_table3.
Note that truncate_table2 does not exist, but I chose truncate_table3 as
a name since it relies on drop_table3.

Reviewers: jkedgar, hermanlee4, spetrunia

Reviewed By: spetrunia

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D53031
george-lorch pushed a commit to george-lorch/percona-server that referenced this pull request May 9, 2016
@yoshinorim
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
33bdf13 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Test Plan:
New test case truncate_table3 and shared with drop_table3.
Note that truncate_table2 does not exist, but I chose truncate_table3 as
a name since it relies on drop_table3.

Reviewers: jkedgar, hermanlee4, spetrunia

Reviewed By: spetrunia

Subscribers: webscalesql-eng

Differential Revision: https://reviews.facebook.net/D53031
inikep pushed a commit to inikep/percona-server that referenced this pull request Apr 23, 2020
@yoshinorim @facebook-github-bot
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
a92063f 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Differential Revision: https://reviews.facebook.net/D53031

fbshipit-source-id: 686be619b81
inikep pushed a commit to inikep/percona-server that referenced this pull request Feb 24, 2021
@yoshinorim @inikep
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
47d5b69 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Differential Revision: https://reviews.facebook.net/D53031

fbshipit-source-id: 686be619b81
inikep pushed a commit to inikep/percona-server that referenced this pull request Nov 15, 2021
@yoshinorim @facebook-github-bot
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
f79f29e 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Differential Revision: https://reviews.facebook.net/D53031

fbshipit-source-id: 553ea7a08e5
ldonoso pushed a commit to ldonoso/percona-server that referenced this pull request Mar 15, 2022
@yoshinorim @inikep
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
6230589 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Differential Revision: https://reviews.facebook.net/D53031
inikep pushed a commit to inikep/percona-server that referenced this pull request Apr 9, 2024
@yoshinorim @inikep
TRUNCATE TABLE to reclaim space in MyRocks (percona#137)
a5b9cec 
Summary:
When truncating a table, space was not really reclaimed in MyRocks.
This was because ha_rocksdb::delete_table() was not called via truncate.
When using HTON_CAN_RECREATE flag, ha_rocksdb::create() should check
if table already exists or not, and delete indexes if exists. This diff
follows the logic.

Differential Revision: https://reviews.facebook.net/D53031
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@hrvojem