Subject Re: performance problem with subquery and "not in" in fb 2.0!!!!
Author crizoo4712
..sorry, but the only issue discussed there is:

The following changes should be noted as possible sources of
performance loss:

ALL predicate may be slow

Formerly, using the ALL existence predicate could return wrong results
in cases where an index was involved. To correct the bug, this version
will never use an index with ALL. This change may degrade performance.

What about "NOT IN"? Or do I have the wrong Release notes version?

Regards, Christoph