Issues
- Modify package to include missing development filesPS-6991Resolved issue: PS-6991illia.pshonkin
- FTS AUX Tables are never encryptedPS-6819Resolved issue: PS-6819
- `SET PERSIST ONLY innodb_sys_tablespace_encrypt`="ON" created an entry in the mysqld-auto.cnf and would cause a server restart to fail.PS-5652Resolved issue: PS-5652Satya Bodapati
- Empty compression dictionaries should be disallowedPS-5546Resolved issue: PS-5546Rahul Malik
- undefined reference to end_cpu_nsecsPS-5457Resolved issue: PS-5457
- [MyRocks] bulk_load_sk test failPS-5455Resolved issue: PS-5455
- Test percona_changed_page_bmp_log_resize is not stablePS-5454Resolved issue: PS-5454Oleksandr Kachan
- 4000x query performance regression in 8.0PS-5449Resolved issue: PS-5449Sveta Smirnova
- Changed page tracking is missing pages changed by the in-place DDLPS-5447Resolved issue: PS-5447Sergei Glushchenko
- FLUSH CHANGED_PAGE_BITMAPS leaves gaps between the last written bitmap LSN and InnoDB checkpoint LSNPS-5446Resolved issue: PS-5446Sergei Glushchenko
- MyRocks - rocksdb_rate_limiter_bytes_per_sec variable cannot be set dynamically from zero valuePS-5444Resolved issue: PS-5444
- MyRocks - Setting Rocksdb_force_flush_memtable_now to any value causes a flushPS-5438Resolved issue: PS-5438
- MyRocks - Not getting more than one immutable memtable when setting MIN_WRITE_BUFFER_NUMBER_TO_MERGE to more than 1PS-5437Resolved issue: PS-5437
- Issue with installing TokuBackup on Percona-server docker image(s)PS-5433Resolved issue: PS-5433Evgeniy Patlan
- Absence of mysql.user leads to auto-apply of --skip-grant-tablesPS-5431Resolved issue: PS-5431
- MyRocks - Write Ahead Log (WAL) is not archived unless rocksdb_wal_ttl_seconds is set to non-zero valuePS-5425
- MyRocks - rocksdb_flush_log_at_trx_commit 0 and 2 seem to have the same behaviorPS-5423Resolved issue: PS-5423
- MyRocks - Rocksdb_wal_size_limit_mb seems to have no impactPS-5422Resolved issue: PS-5422
- Killing a range query on MyRocks creates zombie queriesPS-5417Resolved issue: PS-5417Lalit Choudhary
- Increase in WHERE clauses causes query planner problemsPS-5416Resolved issue: PS-5416Lalit Choudhary
- jemalloc 5.0.x causes TokuDB/PerconaFT to assert on loadPS-5406Resolved issue: PS-5406George Lorch
- Allow NULL value for rows in column referenced by ts_col to mean "don't filter"PS-5389Resolved issue: PS-5389
- In Percona Server tar.gz I am not able to use keyring_file pluginPS-5385Resolved issue: PS-5385
- Slow startup after an upgrade from MySQL 5.7 to MySQL 8.PS-5379Resolved issue: PS-5379
- Enable RocksDB and TokuDB in Travis config for PS 8.0PS-5376Resolved issue: PS-5376Przemyslaw Skibinski
- buf_pool_zip_hash mutex declared with buf_pool_zip_free keyPS-5369Resolved issue: PS-5369Laurynas Biveinis
- Assertion failure: sync0types.h:981:m_id != LATCH_ID_NONEPS-5358Resolved issue: PS-5358
- LP #1570682: Parallel doublewrite buffer file created when skip-innodb_doublewrite is setPS-3411Resolved issue: PS-3411Kamil Holubicki
Modify package to include missing development files
Description
Environment
Smart Checklist
Activity
Jira Bot May 26, 2020 at 8:55 PM
To:
CC:
Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.
I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.
If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.
This message will be added only once per issue, regardless of how many times
the Summary is edited.
message-code:summary-edited
illia.pshonkin April 24, 2020 at 8:55 AM
It's not recommended as MySQL upstream changelog clearly says that application should use `mysql.h` header file. Instead of making a symlink it's better to open a ticket at application's bugtracker and report it with link to changelog.
uMzwX8An9-kG April 21, 2020 at 12:46 PM
Is it possible to add to packages symlink for save backward capability?
This symlink fixes the error and old application build successful.
illia.pshonkin April 21, 2020 at 12:39 PM
As `my_config_%{_arch}.h` was removed in upstream(8.0.2 version), we remove our `my_config.h`, which points to obsolete header. `mysql.h` should be used instead
illia.pshonkin April 21, 2020 at 12:28 PM
Hi
As upstream MySQL deprecated my_config.h in version 8.0.2, which is no longer included into official builds.
Applications should use mysql.h header for building instead
See: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-2.html
Hello.
Unfortunately package percona-server-devel.x86_64 (checked versions from 8.0.13-4.1.el7 to 8.0.19-10.1.el7 ) does not provide required headers files.
One of missed files is "my_config_x86_64.h", it's included in /usr/include/mysql/my_config.h
Without this file is impossible to build program, which depends on mysql.