SET CONSTRAINTS not schema-aware

SET CONSTRAINTS doesn't allow you to schema-qualify a constraint name.
Here's an example:

create schema test;
create table test.foo (a int primary key);
create table test.bar (b int primary key, c int constraint myconstraint references test.foo);

-- This succeeds even though schema "test" is not in the search path:
set constraints myconstraint immediate;

-- This is what should work:
set constraints test.myconstraint immediate;
ERROR: parser: parse error at or near "." at character 21

Comments?

--
Peter Eisentraut peter_e(at)gmx(dot)net