>FWIW, it isn't going to happen anyway, because the TID scan mechanism >doesn't support scanning based on a join condition. That hasn't gotten >to the top of the to-do list because the use case is almost vanishingly >small. ctids generally aren't stable enough for it to be useful to >store references to one table's ctids in another table.
Thanks for explanation. -- ------------ pasman -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
