Db_update_helper.py:352: Warning: Table 'organizations_orgmemberquota' already exists cursor.execute(sql)

Upgrading Seafile Server CE on CentOS 7
6.0.9 --> 6.3.4

./upgrade_6.0_6.1.sh 
(all OK)

./upgrade_6.1_6.2.sh 
(all OK)

./upgrade_6.2_6.3.sh 

-------------------------------------------------------------
This script would upgrade your seafile server from 6.2 to 6.3
Press [ENTER] to contiune
-------------------------------------------------------------



Updating seafile/seahub database ...

[INFO] You are using MySQL
[INFO] updating ccnet database...
[INFO] updating seafile database...
[INFO] updating seahub database...
/home/seafile/seafile-server-6.3.4/upgrade/db_update_helper.py:352: Warning: Table 'organizations_orgmemberquota' already exists
  cursor.execute(sql)
Done

migrating avatars ...

Done

updating /home/seafile/seafile-server-latest symbolic link to /home/seafile/seafile-server-6.3.4 ...



-----------------------------------------------------------------
Upgraded your seafile server successfully.
-----------------------------------------------------------------

Is the warning important? I saw that in upgrade/sql/4.2.0/mysql/seahub.sql the SQL statement which creates the table is:

 CREATE TABLE IF NOT EXISTS `organizations_orgmemberquota` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `org_id` int(11) NOT NULL,
   `quota` int(11) NOT NULL,
   PRIMARY KEY (`id`),
   KEY `organizations_orgmemberquota_944dadb6` (`org_id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

and in upgrade/sql/6.3.0/mysql/seahub.sql the SQL statement which creates the table is:

CREATE TABLE IF NOT EXISTS `organizations_orgmemberquota` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `org_id` int(11) NOT NULL,
  `quota` int(11) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `organizations_orgmemberquota_org_id_93dde51d` (`org_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

i.e., the difference is that the new script wants the KEY to be organizations_orgmemberquota_org_id_93dde51d instead of organizations_orgmemberquota_944dadb6 but it doesn’t happen, because the table already exists (as the warning says). Is there a problem with that? Should I manually go and change the KEY to organizations_orgmemberquota_org_id_93dde51d? Should I expect any problems if I don’t?