• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Plesk not using indexes in database?

Fabian H

Basic Pleskian
In order to speed up my database I logged all queries not using indexes.
There are many queries from plesk, like this:
Code:
# Time: 211217 16:22:36
# User@Host: admin[admin] @ localhost []
# Thread_id: 99564  Schema: psa  QC_hit: No
# Query_time: 0.000300  Lock_time: 0.000088  Rows_sent: 120  Rows_examined: 120
# Rows_affected: 0  Bytes_sent: 5115
use psa;
SET timestamp=1639754556;
select param, val from misc;

# User@Host: admin[admin] @ localhost []
# Thread_id: 99564  Schema: psa  QC_hit: No
# Query_time: 0.000105  Lock_time: 0.000049  Rows_sent: 1  Rows_examined: 1
# Rows_affected: 0  Bytes_sent: 113
SET timestamp=1639754556;
SELECT `SchemaVersions`.* FROM `SchemaVersions` LIMIT 1;

# User@Host: admin[admin] @ localhost []
# Thread_id: 99564  Schema: psa  QC_hit: No
# Query_time: 0.000213  Lock_time: 0.000090  Rows_sent: 0  Rows_examined: 0
# Rows_affected: 0  Bytes_sent: 11
SET timestamp=1639754556;
DELETE FROM `SessionContexts` WHERE (`sessionId` IN (SELECT `sessions`.`sess_id` FROM `sessions` WHERE (`modified` + `lifetime` < 1639754556)));
So, is Plesk really not using indexes within its database queries?
 
Back
Top