not doing that.
I noticed this, but the view stays unchanged so long time.
I thought it was done intentionally.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
On 24.07.2023 09:42, Pavel Luzanov wrote:
Is IS_GRANTABLE a key column for ROLE_AUTHORIZATION_DESCRIPTORS?
If not, duplicates is not possible. Right?
The answer is: no.
Duplicate pairs (grantee, role_name) is impossible only with defined key
with this two columns.
If there is no such key or
On 09.08.2023 21:06, Bruce Momjian wrote:
On Sun, Jul 23, 2023 at 02:09:17PM +0300, Pavel Luzanov wrote:
Please consider to add item to the psql section:
Add psql \drg command to display role grants and remove the "Member of"
column from \du & \dg altogether (d65ddaca)
The rel
attribute for a role now will affect (as the
default value) only future GRANT commands without an INHERIT clause.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
The only question about "can be". Why not "will be"? The inheritance
behavior will be changed anyway.
Please let me know if I need any other changes. Thanks.
* Allow psql's access privilege commands to show system objects (Nathan
Bossart, Pavel Luzanov)
The options
lay roles \drg - display role grants
But the long history of \du & \dg prevents from doing so, and creating a
third option is too excessive.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
g "Can" instead of "yes" to represent true.
In other psql commands, boolean values are always shown as yes/no.
NULL instead of false might be possible, but I'd rather check if this approach
has been used elsewhere. I prefer consistency everywhere.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
about pg_roles to this
commitfest entry[2].
I will return to work on the patch after my vacation.
1.https://www.postgresql.org/message-id/flat/db1d94ba-1e6e-4e86-baff-91e6e79071c1%40postgrespro.ru
2.https://commitfest.postgresql.org/48/4738/
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
regress_du_admin |
t | t | t | postgres(10 rows)But is it worth inventing a new
psql command for this?
-
Pavel Luzanov
6.
The ADMIN OPTION is available in all supported versions.
* The new meta-command will not show all roles. It will only show the
roles included in other roles.
To show all roles you need to add an outer join between pg_roles and
pg_auth_members.
But all columns except "role" will be left blank. Is it worth doing this?
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
ady to take up this topic. There
is definitely room for improvement here.
But first I want to finish with the \du command.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
On 24.06.2023 18:57, David G. Johnston wrote:
On Sat, Jun 24, 2023 at 8:11 AM Pavel Luzanov
wrote:
There are two commands showing the same information about roles:
\du and
\dr.
I would add \dr as the new official command to complement adding \drg
and deprecate both \du and \dg
Please find attached new patch version.
It implements \drg command and hides duplicates in \du & \dg commands.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
From a117f13fd497bf6ff8a504bcda6cb10d34dd22a7 Mon Sep 17 00:00:00 2001
From: Pavel Luzanov
Date: Mon, 26 Jun 2023 2
more people to chip in.
I am not against moving "Valid until" and "Connection limit" to extended mode.
It just seemed to me that without these two columns, the output of the command
is too short, so there is no reason in hiding them.
But you are right, we need more opinion
On 16.07.2024 16:24, Robert Haas wrote:
Which version of the patch is currently under discussion?
I believe we are talking about the latest v8 patch version. [1]
1.https://www.postgresql.org/message-id/5341835b-e7be-44dc-b6e5-400e9e3f3c64%40postgrespro.ru
--
Pavel Luzanov
Postgres
hat's fine.
So the time for change has not come yet. In any case, this discussion may be
useful
in the future.Butwhoknows,maybenowwecancometosomekindof agreement.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
k I'm not the first one trying to bikeshedding in this area.
It's probably been discussed many times whythisshouldnotbe done.
But such thoughts do come, and I don't know the answer yet.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
On 23.07.2024 15:53, Robert Haas wrote:
On Mon, Jul 22, 2024 at 5:19 PM Pavel Luzanov wrote:
Visible but inaccessible objects in system catalogs increase the volume
of command output unnecessarily. Why do I need to know the list of all
schemas in the database if I only have access to the
TABLE xxx ...
-
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| t | table | postgres=arwdDxt/postgres+| |
| | | u=r/postgres | |
-
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
permissions, they are
not printed by any backslash commands.
I tried your patch. From my point of view this is desirable behavior.
Hopes this patch will be included in v12.
-
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
log | aclremove | aclitem[] | aclitem[], aclitem
-
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
tions.
Your's patch from another thread closes the last hole - describing
default privileges in various psql commands.
-----
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
s a very needed and important feature, but for others
purposes.
-
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
s like my mistake.
I missed that "Initial Data Synchronization" section is a subsection
of "Row filters". There is no hidden reason other than matching
the link name with the subsection name and my inattention.
v2 of proposed patch looks good to me.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
On 22.11.2024 05:52, Michael Paquier wrote:
On Thu, Nov 21, 2024 at 10:50:41PM +0300, Pavel Luzanov wrote:
I found that the help for \pset command missed xheader_width option.
Good catch. This is a mistake from a45388d6e098. The patch should
have used HELP0() as this is a single variable
I found that the help for \pset command missed xheader_width option.
Please, consider this small correction.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
From a5f59e77f3caf5b6bbbfc441393da68999e9e9fc Mon Sep 17 00:00:00 2001
From: Pavel Luzanov
Date: Thu, 21 Nov 2024 22:32:44
Hello,
After reading thread "new commitfest transition guidance"[0],
and as patch author, I decided to write short summary for this
committfest entry[1].
Last patch has version 8, example output and code are here[2].
Proposed approach to \du command has not found positive responses
for several m
ple months later in June,
if no one wants to review it earlier.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
this patch.
Personally, if I were trying to make these things consistent, I'd have
gone in the other direction (ie return empty tables).
+1
Returning empty tables is a more appropriate behavior.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
andsetthe status to
"Waitingon Author". I hope that I will return to this work in June.
Robert's idea (detailed role permissions report with \du rolename) can
be implemented as a separate work.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
way is to preload it into some or all sessions
by including pg_overexplain in session_preload_libraries
or shared_preload_libraries in postgresql.conf.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
101 - 132 of 132 matches
Mail list logo
