0

I have partitioned a table on the basis of a column. This column can either have 0 or 1. So, only two partitions (p0, p1) have been created internally. On this table there are 3 triggers which execute on insert, delete and update event.

Insert trigger - inserting a new record including ID of inserted row in another table.

Update trigger - Manipulate 2 other tables.

Delete trigger - Delete entries from associated tables.

Now, my concerns are below:

  • Do these triggers affect the performance negatively or have no effect?
  • In case of negative affect, what alternate approach I should take?
  • How does MySQL manage these 3 triggers on partitioned tables internally?
  • What measure changes happened in the trigger execution before and after table partition?
  • Your first two questions are unanswerable without knowing what your triggers actually do. A trigger that does nothing will have little impact. A trigger that does monster joins on huge tables might slow things down a wee bit. – Mat Aug 12 '14 at 8:36
  • @Mat, I hae updated my question. – ursitesion Aug 12 '14 at 8:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.