Thank you for a possible solution.<br /><br />But what about the database which exists and works correctly (and
conformsall the standards from the documentation), but dump+restore sequence is failed for it? Does it mean that
pg_dumpshould be improved to pass dump+restore sequence?<br /><br />Besides that, for pg_dump has corresponding
behaviourCONSTRAINT = FOREIGN KEY. <br />For CONSTRAINT = CHECK - it hasn't.<br /><br /><br /><div
class="gmail_quote">OnThu, Nov 13, 2008 at 9:07 PM, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div
class="Ih2E3d">"DmitryKoterov" <<a href="mailto:dmitry@koterov.ru">dmitry@koterov.ru</a>> writes:<br /> > 3.
Thefunction a() calls any OTHER function b() from OTHER namespace (or<br /> > uses operators from other namespaces),
butdoes not specify the schema name,<br /> > because it is in database search_path:<br /><br /> > CREATE FUNCTION
a(iinteger) RETURNS boolean AS $$<br /> > BEGIN<br /> > PERFORM b(); -- b() is is from "nsp" schema<br />
> RETURN true;<br /> > END;$$ LANGUAGE plpgsql IMMUTABLE;<br /><br /></div>I think your function is broken.
Youmight want to fix it by attaching<br /> a local search_path setting to it.<br /><br />
regards,tom lane<br /><font color="#888888"><br /> --<br /> Sent via pgsql-hackers mailing list (<a
href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br/> To make changes to your
subscription:<br/><a href="http://www.postgresql.org/mailpref/pgsql-hackers"
target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></font></blockquote></div><br />