From e33ebe7304341593b396ffea4f994c95c6824a2f Mon Sep 17 00:00:00 2001
From: Girish Ramakrishnan <girish@cloudron.io>
Date: Thu, 22 Mar 2018 21:49:08 -0700
Subject: [PATCH] Revert "mysql: increase max_allowed_packet"

This reverts commit 9123ea70169079bcc079d7f00b822dd3d4dd6b3a.

Not needed. This was a db corruption issue
---
 setup/start/mysql.cnf | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/setup/start/mysql.cnf b/setup/start/mysql.cnf
index e4c061b75..8339fa901 100644
--- a/setup/start/mysql.cnf
+++ b/setup/start/mysql.cnf
@@ -6,7 +6,7 @@
 performance_schema=OFF
 max_connections=50
 # on ec2, without this we get a sporadic connection drop when doing the initial migration
-max_allowed_packet=64M
+max_allowed_packet=32M
 
 # https://mathiasbynens.be/notes/mysql-utf8mb4
 character-set-server = utf8mb4
@@ -15,7 +15,7 @@ collation-server = utf8mb4_unicode_ci
 [mysqldump]
 quick
 quote-names
-max_allowed_packet  = 64M
+max_allowed_packet  = 16M
 default-character-set = utf8mb4
 
 [mysql]