schema level variables and deferrable unique constraints

<br /><font face="sans-serif" size="2">hi!</font><br /><font face="sans-serif" size="2">I apologize for mailing on the
hackerslist but I posted on the general list and did not get a good answer.</font><br /><font face="sans-serif"
size="2">Ihave two independent issues, but am addressing them together.</font><br /><br /><font face="sans-serif"
size="2">1.</font><br/><font face="sans-serif" size="2">Oracle has package level variables which are not mappable to
anypostgres equivalent.</font><br /><font face="sans-serif" size="2">could we have something like schema scope
variableswhich could be directly referred from let's say plpgsql functions?</font><br /><font face="sans-serif"
size="2">Cansomeone give me some pointers on how to go about imlpementing this?</font><br /><br /><font
face="sans-serif"size="2">.</font><br /><font face="sans-serif" size="2">Postgres does not support deferrable unique
constraints.</font><br/><font face="sans-serif" size="2">we would however like to support this especially as some
updatesgive non-standard behavior because of this.</font><br /><font face="sans-serif" size="2">for details please
referto </font>