Re: Installing PL/pgSQL by default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thom Brown <thombrown(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Subject: Re: Installing PL/pgSQL by default
Date: 2009-12-09 03:53:41
Message-ID: 20983.1260330821@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-12-09 05:22:38 Re: how to ensure a client waits for a previous transaction to finish?
Previous Message Dan Kortschak 2009-12-09 03:13:24 Re: how to ensure a client waits for a previous transaction to finish?

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2009-12-09 04:05:43 Re: ProcessUtility_hook
Previous Message Robert Haas 2009-12-09 03:50:50 Re: [PATCH] Windows x64 [repost]