Of course, I checked the triggers of this table. There are not any dependencies or futher updates in them. The size of the table is very modest - less several thousands of records. It is heavily used - both in selects and updates.

The strangest part of the store is this - such unexpected reads appears for only some of the tables. There are other tables (some of them bigger, some of them with more complex triggers) for which the repeated updates do not create excessive reads on Linux server.

Maybe this is some bug...

It is Firebird 2.1.x