Interesting, I've never used pt-online-schema-change with a worry for downstream slaves, it was that there were major tables that drove applications, used my millions a month.
I no longer live in that world, I never had an issue during the drop/swap. And it was a goto for many years. On Sat, Mar 22, 2025 at 1:41 PM Gordan Bobic via discuss < [email protected]> wrote: > ALTER TABLE ... ALGORITHM=INPLACE, LOCK=NONE; > > Unless you have downstream slaves that are lag sensitive. They you'll > probably have to pt-online-schema-change with drop-swap FK handling, but > that is not entirely risk-free (you might get FK violations during the > drop-swap). > > On Sat, 22 Mar 2025, 19:28 edi mari via discuss, < > [email protected]> wrote: > >> Hi, >> I have a 200GB table with a foreign key constraint, and I need to drop an >> existing index and add a non-unique index to it. >> >> What is the best approach to do this with minimal impact on users? >> >> Thanks >> Edi >> _______________________________________________ >> discuss mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > _______________________________________________ > discuss mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
