On 03/21/2016 07:15 AM, Vick Khera wrote:
On Fri, Mar 18, 2016 at 5:46 PM, Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
They should be able to, see below. If that is not your case, then
more information is needed.
You can see your own queries, however non-superuser will not
On Fri, Mar 18, 2016 at 5:46 PM, Adrian Klaver
wrote:
> They should be able to, see below. If that is not your case, then more
> information is needed.
>
You can see your own queries, however non-superuser will not see the query
for other users. You will be able to see the other info, though.
I
On 03/18/2016 01:09 PM, avi Singh wrote:
Guys
Whats the best way to grant select on pg_stat_activity so that
non super user can access this view.
They should be able to, see below. If that is not your case, then more
information is needed.
guest@test=> select current_user;
current_
Guys
Whats the best way to grant select on pg_stat_activity so that non
super user can access this view.
Thanks
Avi
On 12/16/2015 11:58 AM, Jerry Sievers wrote:
spur230 writes:
I am using Postgres 9.4. I created a login role and gave select to all
tables to a schema as follows:
create role fix;
create role dcv login password 'mypassword' in role fix;
grant select on all tables on schema xzy to dcv';
I
spur230 writes:
> I am using Postgres 9.4. I created a login role and gave select to all
> tables to a schema as follows:
>
>
> create role fix;
> create role dcv login password 'mypassword' in role fix;
> grant select on all tables on schema xzy to dcv';
>
> I was able to connect to the dat
I am using Postgres 9.4. I created a login role and gave select to all
tables to a schema as follows:
create role fix;
create role dcv login password 'mypassword' in role fix;
grant select on all tables on schema xzy to dcv';
I was able to connect to the database without giving 'grant conne
On Thursday, September 24, 2015, Maxim Boguk wrote:
>
>
> On Thu, Sep 24, 2015 at 9:28 PM, Alex Magnum > wrote:
>
>> Hi,
>> is it possible to grant select to views and functions without the need to
>> also grant the user the SELECT privileges to the Tables used in the views
>> or functions?
>>
>
On 24 September 2015 at 12:28, Alex Magnum wrote:
> Hi,
> is it possible to grant select to views and functions without the need to
> also grant the user the SELECT privileges to the Tables used in the views or
> functions?
>
> That way I could create read only users on a website and limit their a
On Thursday, September 24, 2015, Alex Magnum wrote:
> Hi,
> is it possible to grant select to views and functions without the need to
> also grant the user the SELECT privileges to the Tables used in the views
> or functions?
>
> That way I could create read only users on a website and limit thei
On Thu, Sep 24, 2015 at 9:28 PM, Alex Magnum wrote:
> Hi,
> is it possible to grant select to views and functions without the need to
> also grant the user the SELECT privileges to the Tables used in the views
> or functions?
>
> That way I could create read only users on a website and limit thei
Hi,
is it possible to grant select to views and functions without the need to
also grant the user the SELECT privileges to the Tables used in the views
or functions?
That way I could create read only users on a website and limit their access
to the bare minimum.
Thanks in advance for any advise o
On 03/08/2013 07:22 AM, Emi Lu wrote:
Good morning,
I am looking for the command to grant create schema permission for a user.
http://www.postgresql.org/docs/9.2/interactive/sql-grant.html
Thanks.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-general mailing list (pgsql-
Good morning,
I am looking for the command to grant create schema permission for a user.
Thanks.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hallo,
is there a reason why
the grant syntax for views isn't included in the documentation?
(eg REFERENCES doesnt make sense for a view)
cf
http://www.postgresql.org/docs/9.2/static/sql-grant.html
or
\h grant in psql
GRANT INSERT ON view_x TO user_y;
works this for scripting reasons i suppose
(
On 2012-08-27, Stephen Crawford wrote:
> Is there a simple way to grant SELECT privileges to a user for all the
> tables in a database, without having to do it for each table?
grant the role (membership of) a role that already has the priveleges.
--
⚂⚃ 100% natural
--
Sent via pgsql-gener
2012/8/27 Stephen Crawford :
> I see that works for 9, but I'm still in 8.4. But another person just sent
> me a bit of code to do it:
>
just don't use "format" function
execure 'grant select on ' || tn || 'to ';
>
> do $$
> declare tn text;
> begin
> for tn in select c.oid::regclass::text
I see that works for 9, but I'm still in 8.4. But another person just
sent me a bit of code to do it:
do $$
declare tn text;
begin
for tn in select c.oid::regclass::text
from pg_class c join pg_namespace n on n.oid = c.relnamespace
where n.nspname not in ('pg_catalog',
*GRANT *{ { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES |
TRIGGER }
[, ...] | ALL [ PRIVILEGES ] }
ON { [ TABLE ] table_name [, ...]
| *ALL TABLES IN SCHEMA schema_name *[, ...] }
TO { [ GROUP ] role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]
See more on http
Is there a simple way to grant SELECT privileges to a user for all the
tables in a database, without having to do it for each table?
Thanks,
Steve
--
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
--
Sent via pgsql-general mailing list (pgsql-general
You appear to have replied directly to me rather than the list, so I've
cc'd the list.
On 08/21/2012 10:11 PM, Evil wrote:
Dear Craig Ringer And Dear Thom!
THANK YOU VERY MUCH for such Great and easy explanation!
Now everything seems is kk with grants.From now i think i understand
how to sep
Hello List,
First time here also beginner to Postgres.So please forgive me for any mistakes.
I'm pretty sure i have same problem.=>
http://archives.postgresql.org/pgsql-admin/2012-03/msg00105.php
(After searching it i found it)
However it is not solution for me.:( *I'm pretty sure i'm doing somet
On 20 August 2012 19:34, Evil wrote:
> Hello List,
> First time here also beginner to Postgres.So please forgive me for any
> mistakes.
> I'm pretty sure i have same problem.=>
> http://archives.postgresql.org/pgsql-admin/2012-03/msg00105.php
> (After searching it i found it)
> However it is not s
On 08/21/2012 02:34 AM, Evil wrote:
After issusing that revoke from public my postgres user still able to
connect to any database.
Looking at your logs, you tested to see if they could connect to a
database named "onlypostgres", but I didn't see any sign that you had
REVOKEd connect from publ
On Tue, 2011-08-23 at 06:43 -0700, igivanoff wrote:
> Hi,
>
> I have the following situation:
>
> postgres=# create database foo with encoding = 'UTF8';
> postgres=# \c foo
> foo=# CREATE SCHEMA sc;
> foo=# ALTER DATABASE foo SET search_path=sc, pg_catalog;
> foo=# CREATE ROLE usr LOGIN PASSWORD
Hi,
I have the following situation:
postgres=# create database foo with encoding = 'UTF8';
postgres=# \c foo
foo=# CREATE SCHEMA sc;
foo=# ALTER DATABASE foo SET search_path=sc, pg_catalog;
foo=# CREATE ROLE usr LOGIN PASSWORD 'usr' NOINHERIT CREATEDB VALID UNTIL
'infinity';
foo=# grant all privi
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
Thanks for the help. it worked
On Wed, Dec 1, 2010 at 11:10 AM, Gary Chambers wrote:
> akp geek,
>
> > I created a schema , I used pg_restore with postgres as user and restored
> every thing to the new schema I
> > created. Now I want to change the owner ship of the schema and all its
> objects
akp geek,
> I created a schema , I used pg_restore with postgres as user and restored
> every thing to the new schema I
> created. Now I want to change the owner ship of the schema and all its
> objects to a different user
> other than postgres. Is it possible to do that with one command?
In t
Hi All -
I created a schema , I used pg_restore with postgres as user
and restored every thing to the new schema I created. Now I want to change
the owner ship of the schema and all its objects to a different user other
than postgres. Is it possible to do that with one command?
Th
On Thu, Apr 8, 2010 at 1:52 PM, dipti shah wrote:
> techdb=> select * from techtable;
> ERROR: permission denied for relation techtable
> techdb=>
>
> ...and it gives permission denied..!
This should work:
SELECT description from techtable;
UPDATE techtable SET description = 'xyz'
This should n
Ohh...sorry. It works but I am wondering why pg_namespace doesn't display
any information.
techdb=> select description from techtable;
description
-
(0 rows)
techdb=> select number from techtable;
ERROR: permission denied for relation techtable
Thanks a ton.
On Thu, Apr 8, 2010 at
I also tried below:
techdb=# revoke all ON techtable from public;
REVOKE
techdb=# select pc.relname, pc.relacl from pg_class pc, pg_namespace pn
where pc.relnamespace=pn.oid and pn.nspname='techdb' and
pc.relname='techtable';
relname | relacl
---+-
On Thu, Apr 8, 2010 at 1:41 PM, dipti shah wrote:
> Okay. I think I got it but it is not working the way it should. I have given
> select permission on one column but still it is displaying both the columns.
> Could you please tell me what is wrong.
>
>
> techdb=# GRANT SELECT (description), UPDAT
Okay. I think I got it but it is not working the way it should. I have given
select permission on one column but still it is displaying both the columns.
Could you please tell me what is wrong.
techdb=# GRANT SELECT (description), UPDATE (description) ON techtable TO
user1;
GRANT
sysdb=> select *
Yup. I read it and tired couple of ways but couldn't figured out how to
specify column names. It gives me below error message and hence, I asked for
the example.
GRANT { { SELECT | INSERT | UPDATE | REFERENCES } ( *column* [, ...] )
[,...] | ALL [ PRIVILEGES ] ( *column* [, ...] ) }
ON [ T
On Apr 8, 2010, at 4:22 , dipti shah wrote:
> Hi, from postgesql features list mentioned at
> http://www.postgresql.org/about/press/features84.html, I came to know that
> it is possible to grant column level permissions.
> Could anyone please give me the example of how to grant column level
>
Hi, from postgesql features list mentioned at
http://www.postgresql.org/about/press/features84.html, I came to know that
it is possible to grant column level permissions.
PostgreSQL is "the most secure by default" and part of that is making
security tools easy to use. 8.4 makes our existing connec
Hi,
I will explain what I need with a simple example.
I have three tables:
jobs, people, cities
I have to grant select on people to john.
GRANT SELECT ON PEOPLE TO JOHN;
Now, when john opens "psql", it can do the selects. That is OK.
But when john does
\d
\d cities
On 2009-05-27, Gauthier, Dave wrote:
> --_000_482E80323A35A54498B8B70FF2B87980040AEFF544azsmsx504amrc_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> What is the (is there a) grant command that I can use to create a super use=
> r without having to
On Wed, May 27, 2009 at 9:19 AM, Gauthier, Dave wrote:
> What is the (is there a) grant command that I can use to create a super
> user without having to specify all the DB objects?
>
> grant all on database foo to thesuper;
>
> and
>
> grant all privileges on database foo to thesuper;
>
> Don’t
Hello
there are not similar statement
if you would to grant rights to more database objects, you have to use
script or stored procedure.
regards
Pavel Stehule
2009/5/27 Gauthier, Dave :
> What is the (is there a) grant command that I can use to create a super user
> without having to specify al
What is the (is there a) grant command that I can use to create a super user
without having to specify all the DB objects?
grant all on database foo to thesuper;
and
grant all privileges on database foo to thesuper;
Don't work.
I know I can achieve what I want by submitting a grant for each and
On Tue, 03 Mar 2009 09:29:17 -0800
John R Pierce wrote:
> Ivan Sergio Borgonovo wrote:
> > I'd like to have different users mainly to have a different
> > search schema path.
> > Things may evolve so this is not going to be the only reason to
> > have more than one user.
> > But I'm faced with t
Ivan Sergio Borgonovo wrote:
I'd like to have different users mainly to have a different search
schema path.
Things may evolve so this is not going to be the only reason to have
more than one user.
But I'm faced with the problem of granting the same access of the
owner of the db to the other use
On Mar 3, 2009, at 4:35 AM, Ivan Sergio Borgonovo wrote:
But I read:
http://www.postgresql.org/docs/8.3/static/sql-grant.html
The SQL standard does not support setting the privileges on more
than one object per command.
This is going to make maintenance and development a PITA every time I
add
I'd like to have different users mainly to have a different search
schema path.
Things may evolve so this is not going to be the only reason to have
more than one user.
But I'm faced with the problem of granting the same access of the
owner of the db to the other users.
But I read:
http://www.po
confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> From: [EMAIL PROTECTED]
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] grant privileges
>
On Saturday 08 November 2008 13:01, Andreas Kretschmer wrote:
> Garry Saddington <[EMAIL PROTECTED]> schrieb:
> > Is there a way to grant all priveleges on all tables and sequences in a
> > database at the same time?
>
Thanks I've just installed pgAdmin and that has done the trick.
Regards
Garry
-
Garry Saddington <[EMAIL PROTECTED]> schrieb:
> Is there a way to grant all priveleges on all tables and sequences in a
> database at the same time?
No, but there are several solutions for that:
14:00 < akretschmer> ??grantall
14:00 < pg_docbot_adz> For information about 'grantall' see:
14:00 <
On 08/11/2008 12:29, Garry Saddington wrote:
> Is there a way to grant all priveleges on all tables and sequences in a
> database at the same time?
Not easily, AFAIK - this question comes up from time to time, and you'll
find in the archives examples of scripts that pull object names from the
sys
Is there a way to grant all priveleges on all tables and sequences in a
database at the same time?
regards
Garry
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Friday 14 March 2008 4:19 am, Kakoli Sen wrote:
> Hello all,
> I'm giving the query
> GRANT ALL PRIVILEGES ON SEQUENCE object_seq TO tester;
> ERROR: syntax error at or near "object_seq" at character 34.
>
> \ds is listing out the sequence.
>
> Regards,
>
> Kakoli
Try:
GRANT ALL PRIVIL
Hello all,
I'm giving the query
GRANT ALL PRIVILEGES ON SEQUENCE object_seq TO tester;
ERROR: syntax error at or near "object_seq" at character 34.
\ds is listing out the sequence.
Regards,
Kakoli
KAKOLI SEN
On Tuesday 04 March 2008, "A Lau" <[EMAIL PROTECTED]> wrote:
> I recently searched for a way to grant permissions to a new created user
> for all tables in a scheme or database. I just found ways who uses psql
> and scripts. But I'm astonished that there is no way to do it with the
> "grant all on
I recently searched for a way to grant permissions to a new created user for
all tables in a scheme or database. I just found ways who uses psql and
scripts. But I'm astonished that there is no way to do it with the "grant
all on database [schema]..."-option. Actually i thought that a grant on a
sc
So, I'm working with some grant/revoke scripts today and occasionally
I see this while running tests:
STATEMENT: GRANT select, insert, update, delete ON public.tablename
TO app;
ERROR: tuple concurrently updated
What's going on? Do I actually need a lock on the table to ensure
this doe
wild_oscar wrote:
Well, after further searching and reviewing the code I believe the problem
was the NOINHERIT in the login role creation.
So the remaining question is:
On another question, if I want to grant privileges to all tables I have to
do them ONE BY ONE. Granting the privileges on the
Dear all,
I'm a bit confused about privilege management in PostgreSQL.
I have a database "db1" , schema "schema1" and table "table1", created with
a superuser.
Now, following the documentation (and what I've learnt about user
management), I created a group called admin and a user login, and gav
Well, after further searching and reviewing the code I believe the problem
was the NOINHERIT in the login role creation.
So the remaining question is:
On another question, if I want to grant privileges to all tables I have to
do them ONE BY ONE. Granting the privileges on the database or the sch
Marcello Verona <[EMAIL PROTECTED]> writes:
> I've a problem with the GRANT on information_schema and view
> "key_column_usage".
> Only a superuser is granted to see the record of this view (and other
> views about index... see table_constraint)
> What kind of permission is necessary for a simple
Hi
I've a problem with the GRANT on information_schema and view
"key_column_usage".
Only a superuser is granted to see the record of this view (and other
views about index... see table_constraint)
What kind of permission is necessary for a simple user?
Thank you!
Marcello
---
Vivek Khera <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE FUNCTION setlogtime(integer) RETURNS void AS $$
>SET log_min_duration_statement = $1;
>SHOW log_min_duration_statement;
> $$ LANGUAGE SQL SECURITY DEFINER;
> How can I write this function?
Use a plpgsql EXECUTE command. In gener
On Mar 14, 2007, at 11:36 AM, Richard Huxton wrote:
Vivek Khera wrote:
I want to do some debugging on an app, and I'd like to set on a
per-connection basis "set log_min_duration_statement = 10;"
Obviously since I'm not super user I get permission denied.
Is there some GRANT I can grant to
Vivek Khera wrote:
I want to do some debugging on an app, and I'd like to set on a
per-connection basis "set log_min_duration_statement = 10;" Obviously
since I'm not super user I get permission denied.
Is there some GRANT I can grant to the user in question to allow this?
I don't really wa
I want to do some debugging on an app, and I'd like to set on a per-
connection basis "set log_min_duration_statement = 10;" Obviously
since I'm not super user I get permission denied.
Is there some GRANT I can grant to the user in question to allow
this? I don't really want to do it globa
Tony Caduto wrote:
> Bruce Momjian wrote:
> > Tony Caduto wrote:
> >
> >> Hi,
> >> I did a quick search and didn't see anything on this, if I missed it
> >> sorry in advance.
> >> Anyway, I was doing a restore of a 8.1 database(on a 8.1 server) using
> >> the 8.2 pg_restore and it was throwing
Bruce Momjian wrote:
Tony Caduto wrote:
Hi,
I did a quick search and didn't see anything on this, if I missed it
sorry in advance.
Anyway, I was doing a restore of a 8.1 database(on a 8.1 server) using
the 8.2 pg_restore and it was throwing errors when it was trying to
restore the permissi
Tony Caduto wrote:
> Hi,
> I did a quick search and didn't see anything on this, if I missed it
> sorry in advance.
> Anyway, I was doing a restore of a 8.1 database(on a 8.1 server) using
> the 8.2 pg_restore and it was throwing errors when it was trying to
> restore the permissions on the seque
Hi,
I did a quick search and didn't see anything on this, if I missed it
sorry in advance.
Anyway, I was doing a restore of a 8.1 database(on a 8.1 server) using
the 8.2 pg_restore and it was throwing errors when it was trying to
restore the permissions on the sequences.
basically the pg_restor
[EMAIL PROTECTED] wrote:
grant all privileges on database test to auser
As far as I can tell this does nothing. Intuitively this command suggests
that the auser would be able to access and modify the database test in
anyway. It would also suggest that as new tables for the database auser
would
On Wed, Dec 13, 2006 at 12:20:03PM -0800, [EMAIL PROTECTED] wrote:
> grant all privileges on database test to auser
>
> As far as I can tell this does nothing. Intuitively this command suggests
> that the auser would be able to access and modify the database test in
> anyway. It would also sugge
grant all privileges on database test to auser
As far as I can tell this does nothing. Intuitively this command suggests
that the auser would be able to access and modify the database test in
anyway. It would also suggest that as new tables for the database auser
would automatically have access
2006/12/13, Tom Lane <[EMAIL PROTECTED]>:
Martijn van Oosterhout writes:
> I don't beleive you have to explicitly grant access to the database, or
> the schema, but you definitly have to grant access to the tables
> directly.
They're completely separate privileges. GRANT ON DATABASE grants or
That would indeed be a handy feature... I was surprised when I discovered
this was not available like in mysql, it's a real pain to grant permissions
to a bunch of tables without querying table metadata.
GRANT ALL ON TABLE *.* TO joeblow
which would indeed be a useful thing to have, bu
Martijn van Oosterhout writes:
> I don't beleive you have to explicitly grant access to the database, or
> the schema, but you definitly have to grant access to the tables
> directly.
They're completely separate privileges. GRANT ON DATABASE grants or
revokes permissions associated with database
On Wed, Dec 13, 2006 at 01:42:32PM +, Tomi N/A wrote:
> I don't get it. I grant all privileges on a database to a role, but
> the server won't let it access the schemas. I grant all privileges on
> the schema to the same role, but the server won't let it access the
> relations in the schema.
>
2006/9/28, Najib Abi Fadel <[EMAIL PROTECTED]>:
when u connect to the database type:
\h GRANT
and you will get all the Grant options:
GRANT { { CREATE | TEMPORARY | TEMP } [,...] | ALL [ PRIVILEGES ] }
ON DATABASE dbname [, ...]
TO { username | GROUP groupname | PUBLIC } [, ...] [ WITH G
On Nov 22, 2006, at 12:19 PM, Wim Bertels wrote:
version 7.4.7
i first grant a group some privileges,
then i take those privileges away from a user in this group,
somehow this doens't work (no errors, but the rights aren't revoked)
eg:
GRANT ALL ON TABLE test TO GROUP groep;
--the user jimmy i
Hallo,
version 7.4.7
i first grant a group some privileges,
then i take those privileges away from a user in this group,
somehow this doens't work (no errors, but the rights aren't revoked)
eg:
GRANT ALL ON TABLE test TO GROUP groep;
--the user jimmy is part of groep;
REVOKE ALL ON TABLE test
when u connect to the database type:\h GRANTand you will get all the Grant options:GRANT { { CREATE | TEMPORARY | TEMP } [,...] | ALL [ PRIVILEGES ] } ON DATABASE dbname [, ...] TO { username | GROUP groupname | PUBLIC } [, ...] [ WITH GRANT OPTION ]This will grant the privileges on all tabl
It seems like it should be a very easy problem to solve I just need one role to have select privileges on all the tables of a particular schema or database including any new tables that are created since they are created programmatically daily. I've combed google and the docs to no avail. Do I need
On Thu, Apr 20, 2006 at 13:52:38 -0300,
Fernan Aguero <[EMAIL PROTECTED]> wrote:
> +[ Bruno Wolff III <[EMAIL PROTECTED]> (19.Apr.2006 14:39):
> |
> |
> | Granting access to a schema allows use of that schema. It does not grant
> | access to objects contained in the schema. You will need to
+[ Bruno Wolff III <[EMAIL PROTECTED]> (19.Apr.2006 14:39):
|
| On Wed, Apr 19, 2006 at 09:29:50 -0300,
| Fernan Aguero <[EMAIL PROTECTED]> wrote:
| >
| > The following works, but I'm not sure about the consequences
| > of granting USAGE to a schema, as the documentation is
| > not clear, IM
On Wed, Apr 19, 2006 at 09:29:50 -0300,
Fernan Aguero <[EMAIL PROTECTED]> wrote:
>
> The following works, but I'm not sure about the consequences
> of granting USAGE to a schema, as the documentation is
> not clear, IMO : "For schemas, allows access to objects
> contained in the specified schema
Hi,
I'm using a database that is splitted into a number of
schemas. In my local installation I'd like to have 3 users:
a dba (ALL privileges), a user with read-write
(INSERT/UPDATE/DELETE on all tables and views and SELECT on
all sequences) privileges and a user with read-only (SELECT
on all table
No, but Veil allows you do it:
http://veil.projects.postgresql.org/
Be warned, implementing column or row-level privileges is not trivial.
If you are sure you need to do it and want to try Veil, I'll give you
what help I can.
__
Marc
On Fri, 2006-03-17 at 11:50 -0400, [EMAIL PROTECTED]
wrote:
>
Sean Hamilton wrote:
Does Postgres support granting priviliges at the column level?
ex. grant update on tableA (id, description) to user
... Or, perhaps with a before-update trigger.
--
Richard Huxton
Archonet Ltd
---(end of broadcast)---
T
Sean Hamilton wrote:
Does Postgres support granting priviliges at the column level?
ex. grant update on tableA (id, description) to user
No, but you can do something similar with views + rules and granting
permissions on that.
--
Richard Huxton
Archonet Ltd
---(
Does Postgres support granting priviliges at the column level?
ex. grant update on tableA (id, description) to user
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMA
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
1 - 100 of 162 matches
Mail list logo
