Percona Server moved to https://jira.percona.com/projects/PS

innodb_expand_import should be boolean

Bug #706719 reported by Valentine Gostev on 2011-01-23

This bug affects 1 person

	Status	Importance	Assigned to
Percona Server moved to https://jira.percona.com/projects/PS	Status tracked in 5.7
5.1	Won't Fix	Low	Unassigned
5.5	Triaged	Low	Unassigned
5.6	Invalid	Undecided	Unassigned
5.7	Invalid	Undecided	Unassigned

In Percona Server variable innodb_expand_import has integer type and requires additional parameter to enabled ('0' or '1' parameter is applicable)

I suggest this variable to be boolean (like innodb_file_per_table)

Valentine Gostev (longbow) on 2011-01-23

Valentine Gostev (longbow) on 2011-05-02

Changed in percona-server:
milestone:	release-5.1.54-12.5 → none

Revision history for this message

Swany (greenlion) wrote on 2011-05-02:

There are other configuration parameters this affects too.

These two come to mind:
innodb-flush-neighbor-pages=0
innodb-ibuf-active-contract=1

Valentine Gostev (longbow) on 2011-05-15

Changed in percona-server:
status:	New → Confirmed

Stewart Smith (stewart) on 2011-05-25

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-25:

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2600

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.