Re: pg_dump and languages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: aklaver(at)comcast(dot)net
Cc: pgsql-general(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: pg_dump and languages
Date: 2004-11-26 23:11:10
Message-ID: 20077.1101510670@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <aklaver(at)comcast(dot)net> writes:
> Sorry should have been more explicit. The dump loaded functions depending on
> plsh before the function that created the language. In fact it did not
> instalI the language at all.

Ah. Looking back at your first message, I see you'd installed plsh into
the pg_catalog schema rather than a user schema. pg_dump specifically
doesn't dump anything that appears in pg_catalog; it assumes all of that
stuff is supplied by the system. So the above is expected behavior.

I haven't looked at plsh, but if it installs stuff directly into
pg_catalog, I'd call that a mistake. At least it shouldn't be the
default behavior.

(Note for pedantry's sake: a language doesn't really belong to any
particular schema; but its support functions do, and pg_dump treats
the language as belonging to the same schema as the support functions.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-11-26 23:39:16 Re: Regexp matching: bug or operator error?
Previous Message Carlos Roberto Chamorro Mostacilla 2004-11-26 22:55:54 Calling function dynamic