Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pabhg-0004ol-Mp for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 12:18:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pabhf-00048u-IH for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 12:18:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pabhf-00048l-3Y for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 12:18:31 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pabhc-0007eW-5x for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 12:18:30 +0000 Received: from [192.168.0.104] (unknown [62.217.188.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id 3246921CD9B0; Fri, 10 Mar 2023 15:18:27 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1678450707; bh=3CEHrqOud4u81yF1O2xieGZLwLD/hrPFON7yCHYlCoo=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=OTOXQ9eS9Tv+45Q8gnmqC+nUG4q242mVA/oYg0YfwJ2h9wuAcZfKWj0rTuAgTBuM9 F9F/dkaVsOwWKXynJv/dqiVw8Sg+fPsIyfpJNxXwtna6NRbYMKmA1fnf0LxIYJiQKk XygkY2IoHihmzEFt78WhlgZbkonPoL8Qd0F29GNQ= Content-Type: multipart/alternative; boundary="------------ETdt6GofyTKDI7qgIOnaQowC" Message-ID: <31cf6b16-ff7f-0afd-5233-702368bd540d@postgrespro.ru> Date: Fri, 10 Mar 2023 15:18:26 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: psql: Add role's membership options to the \du+ command Content-Language: en-US To: "David G. Johnston" Cc: David Zhang , "pgsql-hackers@lists.postgresql.org" References: <01620d6b-9efe-b199-b619-8450d865ec83@postgrespro.ru> <94ce7392-fa90-bc1c-4dc2-677161bbff58@postgrespro.ru> <20824093-d94f-e5d6-b611-8cec7fc6e95e@postgrespro.ru> From: Pavel Luzanov In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------ETdt6GofyTKDI7qgIOnaQowC Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 08.03.2023 00:02, David G. Johnston wrote: > > FWIW I've finally gotten to publishing my beta version of the Role > Graph for PostgreSQL pseudo-extension I'd been talking about: > > https://github.com/polobo/RoleGraphForPostgreSQL Great. So far I've looked very briefly, but it's interesting. > I handle EMPTY explicitly in the Role Graph but as I noted somewhere > in my comments, it really shouldn't be possible to leave the database > in that state.  Do we need to bug Robert on this directly or do you > plan to have a go at it? I don't plan to do that. Right now I don't have enough time and experience. This requires an experienced developer. -- Pavel Luzanov Postgres Professional:https://postgrespro.com --------------ETdt6GofyTKDI7qgIOnaQowC Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 08.03.2023 00:02, David G. Johnston wrote:

FWIW I've finally gotten to publishing my beta version of the Role Graph for PostgreSQL pseudo-extension I'd been talking about:


Great. So far I've looked very briefly, but it's interesting.

I handle EMPTY explicitly in the Role Graph but as I noted somewhere in my comments, it really shouldn't be possible to leave the database in that state.  Do we need to bug Robert on this directly or do you plan to have a go at it?

I don't plan to do that. Right now I don't have enough time and experience. This requires an experienced developer.
-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com
--------------ETdt6GofyTKDI7qgIOnaQowC--