lost trigger when setting up multiple queue-tables within the same schema

[LudoDaemen]

Expected Behavior

Have completely functional queue-tables when having multiple ones

Actual Behavior

The sql-script for setting up the table sets up the trigger without having a refererence to the name of the table the trigger is associated with. That leads to the earliest defined table to loose its trigger when setting up the second one.

Solution seems relatively simple : in the sql-script make the table name a part of the trigger name.