trove/releasenotes/notes/deprecate-long-query-time-b85af24772e2e7cb.yaml
Petr Malik 665bdaefc1 Deprecate 'guest_log_long_query_time'
Slow query time should be configurable on per-instance basis
via the existing configuration group mechanism (see the bug).

We need to deprecate the existing global conf property first.
The property has been deprecated on all datastores.

Validation rules have been updated on those that
support log retrieval as well:

  - MySQL: long_query_time
  - Percona: long_query_time
  - Percona XtraDB Cluster: long_query_time
  - PostgreSQL: log_min_duration_statement
  - MariaDB: long_query_time

The logging settings will be saved with lower 'priority' than
any user settings. This will ensure the user settings
(if present) always override the global value.
Once the deprecated options go away we can again apply
the logging settings at the system level.

Change-Id: I9c28ceb933b6819b8e96556584b2e26cab2155fb
DocImpact: Document deprecated properties
Partial-Bug: 1542485
2016-08-17 15:59:53 +00:00

13 lines
391 B
YAML

---
deprecations:
- Make 'long query time' manageable via
configuration groups (see bug 1542485).
Deprecate the global 'guest_log_long_query_time'
option in preference of datastore-specific
configurations.
MySQL long_query_time
Percona long_query_time
Percona XtraDB Cluster long_query_time
MariaDB long_query_time
PostgreSQL log_min_duration_statement