The references are all to the same table i.e. they are employee ids, so leaving some and not others would make no sense. The table has no deletes, small amount of inserts and moderate amount of updates. However there are many selects and its their performance I am most concerned with.
Foreign keys have no impact on selects.
Although this does sound like a rather strange design to me (20+ columns wide and they're all employee ids?)
There are more than 20 fieldss. Its a report that can get updated by different employees and we wish to keep a record of which employee completed which section. Couldn't think of any other way to do it.
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
