"Tom Lane" <tgl@sss.pgh.pa.us> writes:
> Lastly, int4notin() and oidnotin() have no permission checking, which
> means you can find out whether specific values are or are not present
> in an int4 or oid column you shouldn't read. This code is so old,
> crufty, and undocumented that I'm strongly inclined to remove it
> instead of fix it --- it really has no excuse to live when we support
> IN (sub-SELECT) constructs.
>
> Comments?
Wow, those are strange beasts.
-- Gregory Stark EnterpriseDB http://www.enterprisedb.com
