Tom Lane wrote:
Perhaps it would be better to initialize needRecheck to the opclass RECHECK flag value? If the consistent function does nothing, the behavior is the same as before, but it can flip the flag in either direction if it wants.
I remember that last spring, in the context of GIT, you were worried about the performance implication of preparing to recheck rows when no rechecks are needed. I didn't quite buy that back then, but this would have the same issue.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
