> How can I find out what this object is?
This query might help if the object is a table:
SELECT c.relname as table,
a.rolname as owner,
c.relacl as permits
FROM pg_class c
JOIN pg_authid a ON ( a.OID = c.relowner )
WHERE relname NOT LIKE 'pg_%'
AND relname NOT LIKE 'informatio
On 8/17/19 4:56 PM, stan wrote:
I am creating an application that will need to have access control. There
will basically be the groups (roles ?):
* normal user (can do insert on a limited sate of tables, and select on a
slightly larger set
* project manager will have some increased insert and s
I am creating an application that will need to have access control. There
will basically be the groups (roles ?):
* normal user (can do insert on a limited sate of tables, and select on a
slightly larger set
* project manager will have some increased insert and select capabilities
* sysadmin wil
stan writes:
> I have deleted, what i thought were all the objects referenced by these
> roles,
> but I still get an error saying there is one object they reference.
> How can I find out what this object is?
The error should tell you, if you're connected to the database where
that object is.
r
I created some roles that I think are badly named, as my understanding of
them increases.
I have deleted, what i thought were all the objects referenced by these roles,
but I still get an error saying there is one object they reference.
How can I find out what this object is?
--
"They that
From: Adrian Klaver
Sent: Sunday, January 27, 2019 8:18:08 PM
To: Begin Daniel
Cc: pgsql-general
Subject: Re: Error message restarting a database
On 1/27/19 2:45 PM, Begin Daniel wrote:
>> If you go to PGDATA.pg_tblspc do you have links to the tablespaces?
>>
>> I only installed one instance of
On Sat 2019-08-17 10:32:40 -0700, Adrian Klaver wrote:
> > I know this query can time out, and it does, resulting in the error I
> > expect: "canceling statement due to statement timeout". The problem is
> > occasionally I see this other error: "canceling statement due to user
> > request".
> >
>
On 8/16/19 2:02 PM, Will Storey wrote:
Hi!
I have a query that fails due to this error and I'm trying to understand
why.
My understanding is I should only see this error if I cancel a query
manually, such as with kill -INT or with pg_cancel_backend(). However I
can't find anything doing that.
On 8/16/19 12:57 PM, David Wall wrote:
In JDBC (latest version), I'm using the
org.postgresql.jdbc.PgConnection.getTransactionState() that returns an
enumeration of IDLE, OPEN or FAILED.
I am familiar with IDLE, meaning the connection has a new transaction
started, but isn't doing anything.
On Fri, Aug 16, 2019 at 11:57 PM Bikram MAJUMDAR
wrote:
> When I go to the URL link for pgwatch that you have given I see the following
> : How do I get to pgwatch docker download and install on my linux server?
I don't want to be harsh, but you should start doing your homework and
report about
stan writes:
> Just starting to expore setting up roles & useres. I ran this statement:
> GRANT CONNECT ON DATABASE stan TO employee;
> But yet \du still reports:
> employee| Cannot login
> What am I doing wrong?
That's not a permissions issue, it's a role-property issue; the
role is
> On Aug 17, 2019, at 9:45 AM, stan wrote:
>
> Just starting to expore setting up roles & useres. I ran this statement:
>
> GRANT CONNECT ON DATABASE stan TO employee;
>
> But yet \du still reports:
>
> employee| Cannot login
>
> What am I doing wrong?
>
> --
> "They that would
Just starting to expore setting up roles & useres. I ran this statement:
GRANT CONNECT ON DATABASE stan TO employee;
But yet \du still reports:
employee| Cannot login
What am I doing wrong?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty n
13 matches
Mail list logo
