innodb_page_size can not be increased after the fact. In order to actually make that change would involve dumping all the databases and re-initializing mysql with the new page size in place, then reloading from all the dumps. I'm not working with a dedicated database server, it's got quite a lot on it other than mailman, so that would be an enormous undertaking.
-Joel
On 12/27/20 3:12 AM, Torge Riedel wrote:
Am 26.12.20 um 23:00 schrieb Joel Lord:
but now we're up and running
Nice to hear, but I fear you could be hit by this issues again, depending on changes in the future on the table. Either when more columns are added or on runtime when rows are added / updated.
I've read the following documentation, but I do not clearly understand whether innodb_page_size can be increased later via config or not:
https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb...
@Mark: Would it be a good approach to split the table 'mailinglist'? I see some groups of columns like "bounce_*" or "dmarc_*" which could be managed in separate tables.
Whereas reaching limits on upgrade is already annoying enough, reaching limits on runtime can be fatal. I guess.
Kind regards Torge
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Joel Lord