Bruce Momjian <bruce@xxxxxxxxxx> writes: > On Wed, Jun 13, 2012 at 03:21:17PM -0500, Merlin Moncure wrote: >> IMNSHO, it's a no-brainer for the todo (but I think it's more >> complicated than adding some comparisons -- which are working now): > I see. Seems we have to add index smarts to those comparisons. That > might be complicated. Uh, the whole point of a TID scan is to *not* need an index. What would be needed is for tidpath.c to let through more kinds of TID comparison quals than it does now, and then for nodeTidscan.c to know what to do with them. The latter logic might well look something like btree indexscan qual preparation, but it wouldn't be the same code. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
