From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Sebastian P(dot) Luque" <spluque(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: extensions in 9.1 |
Date: | 2011-09-20 16:18:00 |
Message-ID: | 9350.1316535480@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Sebastian P. Luque" <spluque(at)gmail(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It sounds like you already have the old "unpackaged" version of that
>> module installed.
> How can I check if this is the case? I was getting that same error when
> trying to install the adminpack onto the postgres database (as postgres
> user of course). If I try "CREATE EXTENSION adminpack FROM unpackaged"
> onto the postgres database this way, I get:
> ERROR: extension "adminpack" has no update path from version "unpackaged" to version "1.0"
> and "CREATE EXTENSION tablefunc FROM unpackaged" onto the template1
> database, I get:
> ERROR: function normal_rand(integer, double precision, double precision) does not exist
Well, maybe you had better explain the history of this database a bit
better. It seems like you've got a subset of the tablefunc functions
installed; how did that come to be? And how did the adminpack functions
get in there? Checking the archives, the reason we didn't bother with
an "unpackaged" upgrade path for adminpack is that it's always installed
its functions into the pg_catalog schema, meaning pg_dump wouldn't dump
them, so they should not have been there after an upgrade.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Nelson | 2011-09-20 17:26:57 | \d+ not showing TOAST table size? |
Previous Message | Sebastian P. Luque | 2011-09-20 15:58:00 | Re: extensions in 9.1 |