Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match mysql max_allowed_packet to be same as production #239

Open
Nikschavan opened this issue Nov 30, 2020 · 0 comments
Open

Match mysql max_allowed_packet to be same as production #239

Nikschavan opened this issue Nov 30, 2020 · 0 comments
Labels
bug Existing functionality isn't behaving as expected could have Could be done, or nice to have, low priority for now developer advocacy Developer Advocacy related tasks

Comments

@Nikschavan
Copy link

This can be checked by running the query - SHOW VARIABLES LIKE 'max_allowed_packet';

On prod/dev/staging environments this value is much larger but on local-server this is only 4M, If you import a copy of production/dev database to your local-server it throws constant errors for the query size being larger than the max_allowed_packet

@Nikschavan Nikschavan added the bug Existing functionality isn't behaving as expected label Nov 30, 2020
@PriyaBhatia0210 PriyaBhatia0210 added the could have Could be done, or nice to have, low priority for now label Apr 15, 2021
@yumito yumito removed the cross-team label Nov 23, 2021
@missjwo missjwo added the developer advocacy Developer Advocacy related tasks label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Existing functionality isn't behaving as expected could have Could be done, or nice to have, low priority for now developer advocacy Developer Advocacy related tasks
Projects
None yet
Development

No branches or pull requests

4 participants