From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dropping PL language retains support functions |
Date: | 2012-03-06 04:38:33 |
Message-ID: | 19305.1331008713@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> By doing a DROP CASCADE on plpython2, you drop the user functions, but
> not the support functions.
Well, yeah. The language depends on the support functions, not the
other way around.
> This certainly looks like a bug. Should I work on a patch?
It's not a bug, and it's unlikely you can "fix" it in pg_upgrade without
making things worse.
The long-run plan is that the procedural language and its support
functions are all part of an extension and what you do is drop the
extension. We're not quite there yet. As of 9.1, if you do "create
extension plpython2" to start with, dropping the extension does drop the
support functions too ... but if you use the legacy "create language"
syntax, that doesn't happen, because an extension object isn't created.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2012-03-06 06:07:41 | Re: ECPG FETCH readahead |
Previous Message | Bruce Momjian | 2012-03-06 02:17:47 | Re: pg_upgrade --logfile option documentation |