Re: Installing PL/pgSQL by default

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Bruce Momjian <bruce@momjian.us>

Cc: Andrew Dunstan <andrew@dunslane.net>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Robert Haas <robertmhaas@gmail.com>, Scott Marlowe <scott.marlowe@gmail.com>, Thom Brown <thombrown@gmail.com>, PGSQL Mailing List <pgsql-general@postgresql.org>, pgsql-hackers@postgresql.org, Craig Ringer <craig@postnewspapers.com.au>

Date: 2009-12-09T03:53:41Z

Lists: pgsql-hackers, pgsql-general

Bruce Momjian <bruce@momjian.us> writes:
> I installed PL/pgSQL by default via initdb with the attached patch.  The
> only problem is that pg_dump still dumps out the language creation:
> 	CREATE PROCEDURAL LANGUAGE plpgsql;
> 	ALTER PROCEDURAL LANGUAGE plpgsql OWNER TO postgres;
> What is odd is that I used the same process that initdb uses to create
> other objects.  Does anyone know why this is happening?

I think pg_dump pays attention to what schema the objects are in,
and that's most likely creating them in PUBLIC.  Try adding
"set search_path = pg_catalog".

It's not impossible that we'll have to tweak pg_dump a bit; it's
never had to deal with languages that shouldn't be dumped ...

			regards, tom lane