Re: taking long time to ALTER the table

[Rick James]

I do not have a handle on the "1 minute for 4M rows", but here are some things that should help.

It is generally not a good design to have "arrays" (such as multiple addresses, _01/_02, list of dates, etc) in a single table. It is better to have other tables, with a PRIMARY KEY that is a combination of the Primary key of this table, plus some other indicator. (For the addresses: 'c' vs 'rb'.)

Furthermore, everything(?) is NULL. This may imply that everything is optional. If so, then moving chunks of optional stuff to another table(s) could clean up the structure. Rather than having lots of NULLs in the other table, simply don't have the row. To put things back together, use LEFT JOIN.

There are 13 names.

ps_key vs ps_id ? Sounds redundant?

Curious... Your first output had a few dy_ fields; the CREATE TABLE has none. Probably the dy_ clump should be another table.

ALTERing a narrower/shorter table should be faster.