> My guess is that it has something to do with the join to the table
> 'mandate'. If your view definition includes a CASE WHEN... that would
My new guess is something to do with permissions being cached
somewhere, because this morning when I tried it (SET followed by
SELECT from page_startup) fro
Kevin Field writes:
> My guess is that it has something to do with the join to the table
> 'mandate'.
I was wondering about that too, but the error message is pretty clear
about which table it's complaining about.
Please see if you can put together a self-contained example.
On Nov 1, 4:39 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Kevin Field writes:
> > Strange, no? Anybody have any ideas why this might be?
>
> Worksforme:
>
> regression=# create group "user";
> CREATE ROLE
> regression=# create group extranet_user in group "user";
> CREATE ROLE
> regression=# crea
Kevin Field writes:
> Strange, no? Anybody have any ideas why this might be?
Worksforme:
regression=# create group "user";
CREATE ROLE
regression=# create group extranet_user in group "user";
CREATE ROLE
regression=# create user x in group extranet_user;
CREATE ROLE
regression=# create view pag
Hi everyone,
I'm having a strange issue on PostgreSQL 9.0.1 on Windows Server 2003
SP2.
I connect as a superuser and then SET SESSION AUTHORIZATION to user
"X" who is a member of group role "extranet_user" which inherits
membership from group role "user". "X", "extranet_user", and even
"user" ar
