2 added 503 characters in body
source | link

Have you posted the question on the Percona forums? Someone there should know for sure if there's a way to make it work with existing triggers.

Are you using replication? If you can get the trigger disabled on the master, but enabled on the slave, the application could read booking_status_changes from the slave.

Can the application change so the trigger isn't needed?

Have you looked at gh-ost as an alternative to pt-online-schema-change? https://github.com/github/gh-ost. It's replication based, so having exiting triggers wouldn't be a problem.

Good Luck!

Edit: I'll rephrase as statements...

You hit a limitation in pt-online-schema-change. Your options:

  • Take downtime for a normal alter
  • Alter the table on all the slaves first, and perform slave promotion
  • Change the application to not require the trigger
  • Use gh-ost instead of pt-online-schema-change, since it does not rely on triggers
  • Disable the trigger on the master, and let the trigger fire on a Slave, reading the queued changes from the slave. Probably not ideal.

Have you posted the question on the Percona forums? Someone there should know for sure if there's a way to make it work with existing triggers.

Are you using replication? If you can get the trigger disabled on the master, but enabled on the slave, the application could read booking_status_changes from the slave.

Can the application change so the trigger isn't needed?

Have you looked at gh-ost as an alternative to pt-online-schema-change? https://github.com/github/gh-ost. It's replication based, so having exiting triggers wouldn't be a problem.

Good Luck!

Have you posted the question on the Percona forums? Someone there should know for sure if there's a way to make it work with existing triggers.

Are you using replication? If you can get the trigger disabled on the master, but enabled on the slave, the application could read booking_status_changes from the slave.

Can the application change so the trigger isn't needed?

Have you looked at gh-ost as an alternative to pt-online-schema-change? https://github.com/github/gh-ost. It's replication based, so having exiting triggers wouldn't be a problem.

Good Luck!

Edit: I'll rephrase as statements...

You hit a limitation in pt-online-schema-change. Your options:

  • Take downtime for a normal alter
  • Alter the table on all the slaves first, and perform slave promotion
  • Change the application to not require the trigger
  • Use gh-ost instead of pt-online-schema-change, since it does not rely on triggers
  • Disable the trigger on the master, and let the trigger fire on a Slave, reading the queued changes from the slave. Probably not ideal.
1
source | link

Have you posted the question on the Percona forums? Someone there should know for sure if there's a way to make it work with existing triggers.

Are you using replication? If you can get the trigger disabled on the master, but enabled on the slave, the application could read booking_status_changes from the slave.

Can the application change so the trigger isn't needed?

Have you looked at gh-ost as an alternative to pt-online-schema-change? https://github.com/github/gh-ost. It's replication based, so having exiting triggers wouldn't be a problem.

Good Luck!