pgsql: Implement a preliminary 'template' facility for procedural - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Implement a preliminary 'template' facility for procedural
Date
Msg-id 20050905235049.A87DAD7BC2@svr1.postgresql.org
Whole thread Raw
Responses Re: pgsql: Implement a preliminary 'template' facility for procedural  (David Fetter <david@fetter.org>)
List pgsql-committers
Log Message:
-----------
Implement a preliminary 'template' facility for procedural languages,
as per my recent proposal.  For now the template data is hard-wired in
proclang.c --- this should be replaced later by a new shared system
catalog, but we don't want to force initdb during 8.1 beta.  This change
lets us cleanly load existing dump files even if they contain outright
wrong information about a PL's support functions, such as a wrong path
to the shared library or a missing validator function.  Also, we can
revert the recent kluges to make pg_dump dump PL support functions that
are stored in pg_catalog.
While at it, I removed the code in pg_regress that replaced $libdir
with a hardcoded path for temporary installations.  This is no longer
needed given our support for relocatable installations.

Modified Files:
--------------
    pgsql/doc/src/sgml/ref:
        create_language.sgml (r1.39 -> r1.40)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_language.sgml.diff?r1=1.39&r2=1.40)
        createlang.sgml (r1.35 -> r1.36)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/createlang.sgml.diff?r1=1.35&r2=1.36)
    pgsql/doc/src/sgml:
        xplang.sgml (r1.28 -> r1.29)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/xplang.sgml.diff?r1=1.28&r2=1.29)
    pgsql/src/backend/commands:
        proclang.c (r1.60 -> r1.61)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/proclang.c.diff?r1=1.60&r2=1.61)
    pgsql/src/backend/parser:
        gram.y (r2.509 -> r2.510)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.509&r2=2.510)
    pgsql/src/bin/pg_dump:
        pg_dump.c (r1.419 -> r1.420)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.419&r2=1.420)
        pg_dump.h (r1.120 -> r1.121)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.h.diff?r1=1.120&r2=1.121)
    pgsql/src/bin/scripts:
        createlang.c (r1.19 -> r1.20)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/createlang.c.diff?r1=1.19&r2=1.20)
    pgsql/src/test/regress:
        pg_regress.sh (r1.59 -> r1.60)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/pg_regress.sh.diff?r1=1.59&r2=1.60)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Back out prior patch and instead just suppress SubqueryScan
Next
From: David Fetter
Date:
Subject: Re: pgsql: Implement a preliminary 'template' facility for procedural