On Mon, 24 Mar 2025 at 18:15, Kristian Nielsen <knielsen@knielsen-hq.org> wrote:
Gordan Bobic via discuss <discuss@lists.mariadb.org> writes:
On Mon, 24 Mar 2025 at 16:40, edi mari <edim2525@gmail.com> wrote:
For example, on the master, we could disable binary logging temporarily:
-- Disable binary logging for the current session SET sql_log_bin = 0; -- Run the CREATE INDEX command CREATE INDEX ix_index ON t1 (col1, col2) ALGORITHM=INPLACE, LOCK=NONE; -- Re-enable binary logging SET sql_log_bin = 1;
You can, but it taints GTID consistency across the server, if you care about that kind of thing.
Gordon, I'm curious, what do you mean here by "taints GTID consistency"?
Doesn't this way exactly preserve GTID consistency, since no new GTIDs will be created on any server when sql_log_bin is set to 0?
The transaction is generated locally on each node, so in theory, it would be generated with different server ids. But I guess it doesn't matter if the transaction isn't binlogged so the point is moot unless you are using Galera. -- Gordan Bobic Database Specialist, Shattered Silicon Ltd. https://shatteredsilicon.net