Michael Black wrote:
>
> Ok. What am I missing here? B_USER is a defined Group Role
>
> CREATE ROLE "B_USER"
You used double-quotes here. This will preserve case and any
non-standard identifier characters (spaces, punctuation, etc.)
> TO ROLE B_USER;
And, thus, you need to use them here. W
On Wed, Mar 2, 2011 at 2:30 PM, Michael Black
wrote:
> Ok. What am I missing here? B_USER is a defined Group Role
>
> CREATE ROLE "B_USER"
> NOSUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;
>
>
> GRANT SELECT PRIVILEGES
> ON b.config_itm
> TO ROLE B_USER;
>
> Nets this --
In response to Michael Black :
>
> Ok. What am I missing here? B_USER is a defined Group Role
>
>
> CREATE ROLE "B_USER"
>
> NOSUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;
>
>
> GRANT SELECT PRIVILEGES
>
> ON b.config_itm
>
> TO ROLE B_USER;
>
> Nets this --
Ok. What am I missing here? B_USER is a defined Group Role
CREATE ROLE "B_USER"
NOSUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;
GRANT SELECT PRIVILEGES
ON b.config_itm
TO ROLE B_USER;
Nets this ---
ERROR: syntax error at or near "B_USER"
LI
rg
Subject: Re: FW: [GENERAL] GRANT question
On Sun, Nov 27, 2005 at 08:02:37AM +0100, Egyd Csaba (Freemail) wrote:
> thak you very much! Now it works well.
[...]
> moson.gdb=# select current_schemas(true);
>current_schemas
> -
> {pg_catalog,public}
> (1
On Sun, Nov 27, 2005 at 08:02:37AM +0100, Egyd Csaba (Freemail) wrote:
> thak you very much! Now it works well.
[...]
> moson.gdb=# select current_schemas(true);
>current_schemas
> -
> {pg_catalog,public}
> (1 row)
>
> moson.gdb=# SELECT edenproc_usesysid('probauser');
>
Regards,
-- Csaba Együd
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 26, 2005 10:16 PM
To: Együd Csaba (Freemail)
Cc: pgsql-general@postgresql.org
Subject: Re: FW: [GENERAL] GRANT question
On Sat, Nov 26, 2005 at 09:37:00PM +0100, Egyd Csaba (Freemail) w
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
>> ... it might also be interesting to try
>> select current_schemas(true);
> in case of the admin it results: {pg_catalog,public}. In case of the
> non-admin user: {pg_catalog}!!!
I think that confirms Michael's suggestion that you'
, November 27, 2005 12:07 AM
To: Michael Fuhr
Cc: Együd Csaba; pgsql-general@postgresql.org
Subject: Re: [GENERAL] GRANT question
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Oops, I forgot that \df uses pg_function_is_visible(), so it won't
> show functions that aren't in your searc
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Oops, I forgot that \df uses pg_function_is_visible(), so it won't
> show functions that aren't in your search path. Try this:
Or try
\df *.edenproc_usesysid
I note the lack of "show search_path" for the non-admin user in
your example ... it mig
On Sat, Nov 26, 2005 at 09:37:00PM +0100, Egyd Csaba (Freemail) wrote:
> moson.gdb=> SELECT oid::regprocedure FROM pg_proc WHERE proname ILIKE
> '%eden%';
[...]
> public.edenproc_usesysid(text)
Hmmm...so the function indeed exists in the public schema. What
happens if you call the schema-qualifi
-Original Message-
From: Együd Csaba (Freemail) [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 26, 2005 9:36 PM
To: 'Michael Fuhr'
Subject: RE: [GENERAL] GRANT question
OK, here you are.
---
moson.gdb=> SELECT oid::regprocedure FROM pg_proc
On Sat, Nov 26, 2005 at 09:10:40PM +0100, Egyd Csaba wrote:
> moson.gdb=> \df eden*
>List of functions
> Schema | Name | Result data type | Argument data types
> +--+--+-
> (0 rows)
Oops, I forgot that \df uses pg_function_is_vis
moson.gdb
(1 row)
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 26, 2005 6:28 PM
To: Együd Csaba
Cc: 'Tom Lane'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] GRANT question
On Sat, Nov 26, 2005 at 06:13:21PM +0100, Egyd
On Sat, Nov 26, 2005 at 06:13:21PM +0100, Egyd Csaba wrote:
> Regarding the search_path it is the same in both cases:
>
> # show search_path;
> search_path
> --
> $user,public
> (1 row)
For different users, the above represents *different* search paths
because $user is expanded to t
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
> Regarding the search_path it is the same in both cases:
> # show search_path;
> search_path
> --
> $user,public
> (1 row)
That's not "the same" if the superuser has a self-named schema ...
regards,
ath;
search_path
--
$user,public
(1 row)
What else could cause this problem?
-- csaba
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 26, 2005 5:29 PM
To: Együd Csaba
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] GRANT quest
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
> # select edenproc_usesysid('probauser');
> ERROR: function edenproc_usesysid(text) does not exist
^^
Read the error message: this is not a lack-of-permissions problem.
I'd wonder w
Hi,
As a superuser I created a normal user:
CREATE USER probauser NOCREATEDB NOCREATEUSER;
ALTER GROUP eden_users ADD USER probauser;
a function:
CREATE OR REPLACE FUNCTION edenproc_usesysid(text)
RETURNS int4 AS .
-- Note that the owner of this
Missed one out, ... the script for sequences is:
select 'grant all on '||n.nspname||'.'||c.relname||' to MYUSERNAME;'
from pg_class c, pg_namespace n
where n.oid = c.relnamespace
and c.relkind IN ('S')
and n.nspname in ('SOMESCHEMA1', 'SOMESCHEMA2');
John Sidney-Woollett
Chris Ochs said:
> Is there a shortcut to grant all privileges on a schema and it's objects
> to
> a user without having to issue GRANT statements for each individual
> object
> in the schema? Given all the possible types of objects I doubt it but
> thought I would ask just in case there was a wa
<>How about using phpPgAdmin? Or something like that?
Also, is there a SQL statement that will return all the possible
privileges? Use that in a subselect and then grant WHERE?
Chris Ochs <[EMAIL PROTECTED]> wrote:
Is there a shortcut to grant all privileges on a schema and it's objects to
a use
El Jue 29 Ene 2004 16:26, Barbara Lindsey escribió:
> What permission does a user need to have to query the pg_ tables
> (pg_attribute, pg_class, etc) ? Do they require special permissions?
What kind of queries? Read or Write?
Users have permission to read from most catalog tables. One they can'
What permission does a user need to have to query the pg_ tables
(pg_attribute, pg_class, etc) ? Do they require special permissions?
arbara Lindsey wrote:
What kind of grant do you need to give a user so that they can have
permission to do a "SELECT nextval(ID)" on a sequence?
I granted the us
I think you should provide an explicit grant (all) on the sequence as
well. The Sequence is an object that is distinct from the table that uses
it.
John Sidney-Woollett
Barbara Lindsey said:
> What kind of grant do you need to give a user so that they can have
> permission to do a "SELECT nextval
Yay! It works.
Thank you.
Bruno Wolff III wrote:
On Thu, Jan 29, 2004 at 09:52:56 -0500,
Barbara Lindsey <[EMAIL PROTECTED]> wrote:
What kind of grant do you need to give a user so that they can have
permission to do a "SELECT nextval(ID)" on a sequence?
I granted the user SELECT,UPDATE,INSERT,
On Thu, Jan 29, 2004 at 09:52:56 -0500,
Barbara Lindsey <[EMAIL PROTECTED]> wrote:
> What kind of grant do you need to give a user so that they can have
> permission to do a "SELECT nextval(ID)" on a sequence?
> I granted the user SELECT,UPDATE,INSERT,DELETE on all the tables,
> including the o
Mensaje citado por Barbara Lindsey <[EMAIL PROTECTED]>:
> What kind of grant do you need to give a user so that they can have
> permission to do a "SELECT nextval(ID)" on a sequence?
> I granted the user SELECT,UPDATE,INSERT,DELETE on all the tables,
> including the one that has the sequence, bu
What kind of grant do you need to give a user so that they can have
permission to do a "SELECT nextval(ID)" on a sequence?
I granted the user SELECT,UPDATE,INSERT,DELETE on all the tables,
including the one that has the sequence, but the sequence query is
failing on permissions.
--
Barbara E. L
29 matches
Mail list logo
