I wrote: > Argh. The problem query has a plan like this: ... > which means the indexscan has to support mark/restore calls. And it > looks like I blew it on mark/restore support when I taught btree to > handle =ANY conditions natively,
I've committed a patch for this. Thanks for the report!
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
