From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Stefan Schwarzer <stefan(dot)schwarzer(at)unep(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org, 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 14:35:00 |
Message-ID: | 4FF5A614.1060305@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/04/2012 11:20 PM, Stefan Schwarzer wrote:
>>>> 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...
>
Using psql log in as user XXX and run SELECT current_schemas('f');
Do same as the postgres user.
Let us know the results.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Schwarzer | 2012-07-05 14:46:39 | Re: ERROR: function crosstab(unknown, unknown) does not exist |
Previous Message | Robert Klemme | 2012-07-05 12:30:23 | Re: The need for clustered indexes to boost TPC-V performance |