yes ... how can i pass variable * to the function has_schema_privilege(*,
'schema-of-interest', 'usage');
Thanks!
On Thu, Aug 2, 2018 at 12:58 PM, Tom Lane wrote:
> Suresh Raja writes:
> > I'm looking for query which can list all users who have access to a
> > particular schema.
>
>
Hi All:
I'm looking for query which can list all users who have access to a
particular schema.
The user may be granted role, which is turn may have access to the schema.
If the schema name is sch1,
grant select on table sch1.tab1 to role_ro;
grant ALL on table sch1.tab1 to role_rw;
grant
Suresh Raja writes:
> I'm looking for query which can list all users who have access to a
> particular schema.
Something involving
SELECT ... FROM pg_user
WHERE has_schema_privilege(usename, 'schema-of-interest', 'usage');
would probably be what you want.
regards,
Hi,
On 2018-08-02 13:00:16 -0700, Peter Geoghegan wrote:
> On Tue, Jul 31, 2018 at 9:00 PM, Andres Freund wrote:
> > I don't think that's particularly relevant. We should always register an
> > invalidation before the relevant CommandCounterIncrement(), because that
> > is what makes catalog
On Tue, Jul 31, 2018 at 9:00 PM, Andres Freund wrote:
> I don't think that's particularly relevant. We should always register an
> invalidation before the relevant CommandCounterIncrement(), because that
> is what makes catalog changes visible, and therefore requires
> registering invalidations
On 08/02/2018 11:23 AM, Suresh Raja wrote:
yes ... how can i pass variable * to the function
has_schema_privilege(*, 'schema-of-interest', 'usage');
PREPARE schema_user(varchar, varchar) AS SELECT * FROM pg_user
WHERE has_schema_privilege($1, $2, 'create');
EXECUTE schema_user ('aklaver',
> Now once your master A can’t become slave of B.
Isn’t that the exact situation that pg_rewind should take care of?
This email and any attachments may contain confidential information. If you are
not the intended recipient, your use or communication of the information is
strictly prohibited.
Thank you, it works :)
https://github.com/ik5/dotfiles/blob/master/psqlrc
On Wed, Aug 1, 2018 at 9:15 PM, Adrian Klaver
wrote:
> On 08/01/2018 10:55 AM, ik wrote:
>
>> hi,
>>
>> Thank you, it does not effect the terminal title.
>>
>> As Adrian answered me, it is not supported :/
>>
>
> I was
Hi,
I've just been running explain analyze on a slow query and came across
something new to me - a node type of ProjectSet in the plan. What is that?
The plan is here: https://explain.depesz.com/s/4rqA
The query does a cross join of two tables to get every row in one combined
with every row in
On 3 August 2018 at 01:16, Oliver Kohll wrote:
> Ah thanks David, at least I know what it is now. I don't think I have any
> set returning functions though will double check in case there's a joined
> view that has one. Perhaps it could be the something to do with cross
> product which similarly
Sent from Yahoo Mail on Android
- Forwarded Message - From: "Om Prakash Jaiswal"
To: "bucardo-gene...@bucardo.org"
Cc: Sent: Thu, Aug 2, 2018 at 18:56 Subject: How
stop acknowledgement of transmitted data Hi I am running bucardo 4.4 version
on postgresql 9.4.8 RHEL 7.3
Of course! Doh.
On 2 August 2018 at 14:27:02, David Rowley (david.row...@2ndquadrant.com)
wrote:
postgres=# select proretset from pg_proc where proname = 'regexp_matches';
proretset
---
t
t
(2 rows)
On 08/02/2018 04:38 PM, rihad wrote:
Hi all. We see such errors on one of our own (non-system) tables on
Postgres 10.3. They stop both automatic vacuum & automatic analyze not
only on that table, but on all tables & databases (manual vacuuming
works though). Luckily it's a small (but
On 08/02/2018 05:34 PM, rihad wrote:
On 08/02/2018 04:38 PM, rihad wrote:
Hi all. We see such errors on one of our own (non-system) tables on
Postgres 10.3. They stop both automatic vacuum & automatic analyze
not only on that table, but on all tables & databases (manual
vacuuming works
On 08/01/2018 10:53 PM, Alexandru Lazarev wrote:
Hi PG Community,
In my company I found that PG Installation on deployed OS Images are
takne from here: https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/
We are using PG 9.6.5 or 9.6.7 + pgpool + plv8 + others
Some or RPMs for CentOS are
Ah thanks David, at least I know what it is now. I don't think I have any
set returning functions though will double check in case there's a joined
view that has one. Perhaps it could be the something to do with cross
product which similarly creates multiple rows on the right for each row on
the
On 2 August 2018 at 21:17, Oliver Kohll wrote:
> Is there an explanation of ProjectSet anywhere?
Plan node types and what they each do are not very well documented
outside of the source code.
ProjectSet appears when the SELECT or ORDER BY clause of the query.
They basically just execute the
Hi all. We see such errors on one of our own (non-system) tables on
Postgres 10.3. They stop both automatic vacuum & automatic analyze not
only on that table, but on all tables & databases (manual vacuuming
works though). Luckily it's a small (but important) table - less than
1000 rows. Any
18 matches
Mail list logo
