Re: Installing PL/pgSQL by default

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Installing PL/pgSQL by default
Дата
Msg-id 20983.1260330821@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Installing PL/pgSQL by default  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: [HACKERS] Installing PL/pgSQL by default  (Dimitri Fontaine <dfontaine@hi-media.com>)
Re: Installing PL/pgSQL by default  (Bruce Momjian <bruce@momjian.us>)
Список 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

В списке pgsql-general по дате отправления:

Предыдущее
От: Dan Kortschak
Дата:
Сообщение: Re: how to ensure a client waits for a previous transaction to finish?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: how to ensure a client waits for a previous transaction to finish?