Re: priviliges issues

Поиск
Список
Период
Сортировка
От John Scalia
Тема Re: priviliges issues
Дата
Msg-id 091B62ED-5A46-4AD3-BA1A-62A4C9229507@gmail.com
обсуждение исходный текст
Ответ на priviliges issues  (Ankush Chawla <ankushchawla03@gmail.com>)
Ответы Re: priviliges issues  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-admin
A couple of things not noted. First do NOT use the postgres database for any work. That is a system db, not intended for use by any roles. Nor should you use the template0 or template1 databases unless you understand what those are going to do. Now, grant the user the ability to connect to the database, then grant permission to the schema if this table is not in the public schema.

Easiest way:

GRANT ALL ON DATABASE <db name> TO user2;
GRANT ALL ON SCHEMA s1 TO user2:

But again, I wouldn’t use the postgres database for any work.
Jay

Sent from my iPad

On Apr 15, 2020, at 2:05 PM, Ankush Chawla <ankushchawla03@gmail.com> wrote:


hi Pgsql-Admin,

I am new to Postgres and naive in understanding
I tried to create a table in a schema and then given privilege to some other user, still he is not able to access. Below are the things I tried:

postgres=# alter schema s1 owner to user1;
ALTER SCHEMA
postgres=# \c postgres user1
You are now connected to database "postgres" as user "user1".
postgres=# create  table s1.new (a integer);
CREATE TABLE
postgres=# grant select on s1.new to user2
postgres-# ;
GRANT
postgres=# \c postgres user2
You are now connected to database "postgres" as user "user2".
postgres=> select * from s1.new;
ERROR:  permission denied for schema s1
LINE 1: select * from s1.new;
                      ^

Regards
Ankush




On Tue, Apr 14, 2020 at 12:36 PM postadmin2020 S <postgadm2020@gmail.com> wrote:
Thanks To all of you. 

On Mon, Apr 13, 2020, 10:54 PM Jeff Janes <jeff.janes@gmail.com> wrote:
On Sun, Apr 12, 2020 at 8:37 AM postgann2020 s <postgann2020@gmail.com> wrote:
Hi All,

Good Evening.

Could someone please suggest the process to resolve the issue.

Issue : proc state as "Idle_in_transaction"

Env: Postgres 9.5.15
Job Schedulers : Tomcat ( For running procs).

We are using tomcat as scheduler for running few jobs.we are observing one of the proc state as "Idle_in_transaction" and due to this remaining other dependent procs get stucked and causing waiting for ever.

If we ran same proc from psql and pgadmin we could able to run successfully and able to get response and no "Idle_in_transaction" state.

proc: select msg,rescode from schema.proc_name('arg1','arg2');

If you run just this in psql, you will be in autocommit mode.  The statement will run in its own transaction which commit as soon as the statement finishes.

The problem is not with the line you show,  it is in what happens before (a transaction is opened) and after (it is not committed) that line.
 
Cheers,

Jeff


--
Best Regards,
Ankush Chawla

В списке pgsql-admin по дате отправления:

Предыдущее
От: Sahul Hameed
Дата:
Сообщение: Materialized View Estimation in Postgres
Следующее
От: Mohammed Afsar
Дата:
Сообщение: Re: priviliges issues