From: | Stefan Schwarzer <stefan(dot)schwarzer(at)unep(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: ERROR: function crosstab(unknown, unknown) does not exist |
Date: | 2012-07-05 06:20:12 |
Message-ID: | 02A17BAA-25EC-45F9-8A6F-7F9E736BFDDE@unep.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>> Now, when I launch a query which includes "crosstab()" as a postgres user, everything works fine. However, if I launch it as user XXX, it complaints:
>
>> Are you schema qualifying the function name when you use it?
>> If not, does user XXX have schema tablefunc in their search_path?
>
> Also, does user XXX have USAGE permission on the schema containing the
> extension? Usually, if you're going to stick an extension into a schema
> other than public, you're going to want to grant usage on that schema to
> PUBLIC, or at least more than nobody.
Strange thing is that if I specify the schema for the crosstab function:
SELECT * FROM tablefunc.crosstab( 'SEL….
than it works.
The search path is indicated as:
"$user", public, metadata, admin, gis, tablefunc, postgis, topology
I added a GRANT USAGE ON SCHEMA tablefunc TO XXX. Just in case, but this didn't solve the problem. Still wondering why it works for user Postgres, but not for user XXX...
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-07-05 09:06:29 | Re: question about source download site. |
Previous Message | Andreas Kretschmer | 2012-07-05 06:16:00 | Re: seq-scan or index-scan |