Tom Lane wrote: > There is deliberately not a way to override (other than using a > different name for the PL). One of the points of this facility is to > fix up broken PL definitions being imported from old dump files, so > believing what the CREATE LANGUAGE command says is exactly what we > don't want.
I don't doubt that, but I just have a stomach ache with this entire notion of having a hard-coded exception list of the sort "if the user requires this, do this instead". Why don't we just put all PLs that we know of into pg_language to begin with, revoke the permissions, and just let CREATE LANGUAGE fail when the dump is restored? (The dump should restore the permissions, shouldn't it?) At least that would let you alter the "template" using existing means. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
