mirror of
https://github.com/MariaDB/server.git
synced 2026-10-23 18:49:29 +03:00
6c951fea5f
mariadb-upgrade silently dropped EXECUTE grants on sys schema stored functions and procedures. The sys schema install scripts reinstalled every routine with DROP FUNCTION/PROCEDURE IF EXISTS followed by CREATE. DROP cascades to delete the routine's rows in mysql.procs_priv, so any EXECUTE grant a DBA had issued on e.g. sys.table_exists or sys.quote_identifier was lost every time mariadb-upgrade reinstalled the sys schema, even though the routine itself came back unchanged. Fix: replace DROP ... IF EXISTS + CREATE with CREATE OR REPLACE in all 53 sys_schema function/procedure files and in the two templates (templates/function.sql, templates/procedure.sql) so future routines follow the same pattern. CREATE OR REPLACE PROCEDURE/FUNCTION goes through sp_drop_routine_internal(), which only deletes the mysql.proc row and never reaches sp_revoke_privileges() (that is only called from the explicit DROP PROCEDURE/FUNCTION statement), so mysql.procs_priv is left untouched and existing grants survive. This mirrors the pattern already used by sys schema views (CREATE OR REPLACE ... VIEW, since MDEV-9077), which never had this problem. Four of the converted files (functions/format_path.sql, functions/ps_is_account_enabled_57.sql, procedures/ps_setup_reset_to_default.sql, procedures/ps_trace_thread_57.sql) are not referenced by scripts/sys_schema/CMakeLists.txt; they were converted anyway for consistency and have no behavioural effect. As a side effect, a pre-existing UDF whose name collides with a sys routine name is no longer destroyed before the reinstall fails: DROP FUNCTION IF EXISTS resolved the UDF namespace first, silently dropping the UDF and then failing on ER_SP_ALREADY_EXISTS anyway; CREATE OR REPLACE fails immediately on ER_UDF_EXISTS with the UDF intact. scripts/maria_add_gis_sp.sql.in and the sys_config triggers were deliberately left untouched: the GIS procedures are only re-installed at bootstrap time (mariadb-upgrade instead patches their definer in place via UPDATE), and triggers carry no procs_priv rows, so neither is on the code path this bug is about. Added mysql-test/main/mysql_upgrade_sys_routine_grants.test, which grants EXECUTE on sys.table_exists and sys.quote_identifier, overwrites both routine bodies with a marker to prove the upgrade actually reinstalls them (rather than the sys schema install being skipped), runs mariadb-upgrade, and checks both that the grants survived and that the real routine bodies came back. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
80 lines
3.2 KiB
SQL
80 lines
3.2 KiB
SQL
-- Copyright (c) 2014, 2015, Oracle and/or its affiliates. All rights reserved.
|
|
--
|
|
-- This program is free software; you can redistribute it and/or modify
|
|
-- it under the terms of the GNU General Public License as published by
|
|
-- the Free Software Foundation; version 2 of the License.
|
|
--
|
|
-- This program is distributed in the hope that it will be useful,
|
|
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
-- GNU General Public License for more details.
|
|
--
|
|
-- You should have received a copy of the GNU General Public License
|
|
-- along with this program; if not, write to the Free Software
|
|
-- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
|
|
|
DELIMITER $$
|
|
|
|
CREATE OR REPLACE DEFINER='mariadb.sys'@'localhost' FUNCTION format_statement (
|
|
statement LONGTEXT
|
|
)
|
|
RETURNS LONGTEXT
|
|
COMMENT '
|
|
Description
|
|
-----------
|
|
|
|
Formats a normalized statement, truncating it if it is > 64 characters long by default.
|
|
|
|
To configure the length to truncate the statement to by default, update the `statement_truncate_len`
|
|
variable with `sys_config` table to a different value. Alternatively, to change it just for just
|
|
your particular session, use `SET @sys.statement_truncate_len := <some new value>`.
|
|
|
|
Useful for printing statement related data from Performance Schema from
|
|
the command line.
|
|
|
|
Parameters
|
|
-----------
|
|
|
|
statement (LONGTEXT):
|
|
The statement to format.
|
|
|
|
Returns
|
|
-----------
|
|
|
|
LONGTEXT
|
|
|
|
Example
|
|
-----------
|
|
|
|
mysql> SELECT sys.format_statement(digest_text)
|
|
-> FROM performance_schema.events_statements_summary_by_digest
|
|
-> ORDER by sum_timer_wait DESC limit 5;
|
|
+-------------------------------------------------------------------+
|
|
| sys.format_statement(digest_text) |
|
|
+-------------------------------------------------------------------+
|
|
| CREATE SQL SECURITY INVOKER VI ... KE ? AND `variable_value` > ? |
|
|
| CREATE SQL SECURITY INVOKER VI ... ait` IS NOT NULL , `esc` . ... |
|
|
| CREATE SQL SECURITY INVOKER VI ... ait` IS NOT NULL , `sys` . ... |
|
|
| CREATE SQL SECURITY INVOKER VI ... , `compressed_size` ) ) DESC |
|
|
| CREATE SQL SECURITY INVOKER VI ... LIKE ? ORDER BY `timer_start` |
|
|
+-------------------------------------------------------------------+
|
|
5 rows in set (0.00 sec)
|
|
'
|
|
SQL SECURITY INVOKER
|
|
DETERMINISTIC
|
|
NO SQL
|
|
BEGIN
|
|
-- Check if we have the configured length, if not, init it
|
|
IF @sys.statement_truncate_len IS NULL THEN
|
|
SET @sys.statement_truncate_len = sys_get_config('statement_truncate_len', 64);
|
|
END IF;
|
|
|
|
IF CHAR_LENGTH(statement) > @sys.statement_truncate_len THEN
|
|
RETURN REPLACE(CONCAT(LEFT(statement, (@sys.statement_truncate_len/2)-2), ' ... ', RIGHT(statement, (@sys.statement_truncate_len/2)-2)), '\n', ' ');
|
|
ELSE
|
|
RETURN REPLACE(statement, '\n', ' ');
|
|
END IF;
|
|
END$$
|
|
|
|
DELIMITER ;
|