Adrian Klaver wrote:
>On 07/05/2012 07:46 AM, 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:
>
The search path is indicated as:
> If the textual value of search_path (as per "show search_path") lists
> the schema but current_schemas() doesn't, I have to think that you've
> got a permissions problem --- the system will silently ignore any
> search_path entries for which you don't have USAGE permission.
> You said you'd done
> Per Toms suggestion you need to check the permissions on the schema.
> One way to do that is, from psql type the following and enter:
> \dn+
One other thing you might want to verify: Does user XXX have the
PUBLIC schema in their search_path? It is by default, but some people
take it out for sec
On 07/05/2012 07:46 AM, 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:
The search path is indicated as:
"$user", public, metadata, admin, gis, tablefunc, post
Stefan Schwarzer writes:
> Ahh
. Indeed, no "tablefunc" schema in there.
If the textual value of search_path (as per "show search_path") lists
the schema but current_schemas() doesn't, I have to think that you've
got a permissions problem --- the system will silently ignore any
search_path entrie
> 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
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
>>> 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?
>
>
Adrian Klaver writes:
> On 07/03/2012 06:48 AM, 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
On 07/03/2012 06:48 AM, Stefan Schwarzer wrote:
Hi there,
I am using 9.1.3. I inserted the tablefunc extension, into a SCHEMA called
tablefunc, in order to separate it from my tables. I had to create it as
postgres user, but changed than the Owner of both schema and functions to my
user XXX.
Hi there,
I am using 9.1.3. I inserted the tablefunc extension, into a SCHEMA called
tablefunc, in order to separate it from my tables. I had to create it as
postgres user, but changed than the Owner of both schema and functions to my
user XXX.
Now, when I launch a query which includes "crosst
11 matches
Mail list logo
