If we assume that the table looks like this: ``` create table pltable ( pl_id integer primary key, checkbox integer not null, description text collate nocase ); ``` or something of that nature, then you can easily determine how many pages it will take based on the number of bytes. If the number of bytes is less than the page size (usually 4096) then it will all be stored on one page. This is probable I should think. If you create an additional index, then that index will also be stored on a separate page. So minimum I/O would occur without an extra index and using the latter (non-indexed) update. The overhead of having, maintaining, and updating the extra index would likely cost much more (in both CPU and I/O) compared to not having it.