There is no backward link from a heap tuple to it's index entries. So if
you have 3 indexes on a table and do an update, you need at least 2 more
index lookups just to set that bit, if you somehow manage to remember by
what index you found this heap tuple in the first place.
On update-heavy tab
Hi,
probably it's just a stupid idea, but what do you think of this:currently,
most if not all queries with aggregates (count(), sum()) make seq scans
when there are no conditions at all. especially count() is a classic question
on any postgres list.
the reason is - at least that's what I
