CODEWITHSUNDEEP
google-cloud-sql
C. H.
C. H.

Reputation: 59

set enforce-gtid-consistency back to false

anyone has the experience that cloudsql replication change this parameter to true, which doesn't allow multiple statement in a transaction, or create temp table. how do I change it back to false in cloudsql? Thx

Upvotes: 4

Views: 2112

Answers (3)

vitor.avancini
vitor.avancini

Reputation: 111

this is very sad, CREATE TABLE ... SELECT is not an unusual feature to just discard

Upvotes: 0

Daniel Kozlowski
Daniel Kozlowski

Reputation: 11

I have the same issue but its with magento 2. I cannot easily change how they do their queries so the only option to me was to build a msql server in compute engine.

Upvotes: 0

Danny Xu
Danny Xu

Reputation: 189

H., this is Danny from CloudSQL. We switched to use GTID for replication which ensures no data loss during replica creation or failover. It's going to be default after MySQL 5.7. With GTID enabled, the flag "enforce-gtid-consistency" has to be set. When enabled, this option enforces GTID consistency by allowing execution of only those statements that can be logged in a transactionally safe manner. It follows that the operations listed here cannot be used with this option: 1. CREATE TABLE ... SELECT statements 2. CREATE TEMPORARY TABLE statements inside transactions 3. Transactions or statements that update both transactional and nontransactional tables.

If you can share your query, I can help you find a walk-around to separate the temp table from multiple statement transaction. Sorry about the inconvenience.

Upvotes: 1

Related Questions