Documentation to enable Automatic schema changes#4
Open
gabocic wants to merge 7 commits into
Open
Conversation
✅ Deploy Preview for releem-documentation ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
gabocic
force-pushed
the
feature/automatic-schema-changes-user-guide
branch
from
ecb7835 to
e2874ca
Compare
gabocic
force-pushed
the
feature/automatic-schema-changes-user-guide
branch
from
e2874ca to
a59d25f
Compare
drupaladmin
requested review from
drupaladmin
and removed request for
drupaladmin
Collaborator
|
Looks good, let's add it to the sidebar |
gabocic
force-pushed
the
feature/automatic-schema-changes-user-guide
branch
2 times, most recently
from
13de7e5 to
0e603e1
Compare
gabocic
force-pushed
the
feature/automatic-schema-changes-user-guide
branch
from
0e603e1 to
4190584
Compare
gabocic
commented
Jun 13, 2026
|
|
||
| By default the agent **does not** run schema changes from Releem, even when you approve them in the product. For schema changes to be executed on your database server, activate this feature explicitly by setting `enable_exec_ddl` to `true`. | ||
|
|
||
| Before running the schema change against the real table, the agent will perform a dry-run of the change against an empty table with the same structure. This is to guarantee that the operation can run successfully with the intenteded strategy. |
gabocic
commented
Jun 13, 2026
|
|
||
| Before running the schema change against the real table, the agent will perform a dry-run of the change against an empty table with the same structure. This is to guarantee that the operation can run successfully with the intenteded strategy. | ||
|
|
||
| There are some schema changes that the database server can't execute on its own, without blocking the table. An alternative it to use an external tool called [pt-online-schema-change](https://docs.percona.com/percona-toolkit/pt-online-schema-change.html). This tool creates a copy of the table with the intended changes, copies all data to this new table, and swaps it with the existing one, with minimum impact. |
gabocic
commented
Jun 13, 2026
| --- | ||
| ## 4. Extend database user permissions | ||
|
|
||
| The same **MySQL user** the agent already uses for monitoring must have permission to run the approved ALTER statements. Connect to the target database server and run the he GRANT statements below: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation to enable Automatic schema changes