pgsql: Support explicit placement of the temporary-table schema within - Mailing list pgsql-committers

Log Message:
-----------
Support explicit placement of the temporary-table schema within search_path.
This is needed to allow a security-definer function to set a truly secure
value of search_path.  Without it, a malicious user can use temporary objects
to execute code with the privileges of the security-definer function.  Even
pushing the temp schema to the back of the search path is not quite good
enough, because a function or operator at the back of the path might still
capture control from one nearer the front due to having a more exact datatype
match.  Hence, disable searching the temp schema altogether for functions and
operators.

Security: CVE-2007-2138

Tags:
----
REL7_3_STABLE

Modified Files:
--------------
    pgsql/doc/src/sgml/ref:
        create_function.sgml (r1.43 -> r1.43.2.1)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_function.sgml.diff?r1=1.43&r2=1.43.2.1)
    pgsql/doc/src/sgml:
        release.sgml (r1.163.2.41 -> r1.163.2.42)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.163.2.41&r2=1.163.2.42)
        runtime.sgml (r1.147.2.8 -> r1.147.2.9)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.147.2.8&r2=1.147.2.9)
    pgsql/src/backend/catalog:
        namespace.c (r1.38.2.2 -> r1.38.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/namespace.c.diff?r1=1.38.2.2&r2=1.38.2.3)
    pgsql/src/test/regress/expected:
        temp.out (r1.5 -> r1.5.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/temp.out.diff?r1=1.5&r2=1.5.2.1)
    pgsql/src/test/regress/sql:
        temp.sql (r1.3 -> r1.3.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/temp.sql.diff?r1=1.3&r2=1.3.2.1)