> I know the table has to be visitied at some point to serve the MVCC, but why > so early? Can NOT ESISTS only be fixed by the table, because it could miss > soemthing otherwise?
Possibly because the index entries you're anti-joining against may point to deleted tuples, so you would erroneously omit rows from the join result if you skip the visibility check? --- Maciek Sakrejda | System Architect | Truviso 1065 E. Hillsdale Blvd., Suite 215 Foster City, CA 94404 (650) 242-3500 Main www.truviso.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
