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 1qD4zg-0001pv-RH for pgsql-hackers@arkaria.postgresql.org; Sat, 24 Jun 2023 15:16:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qD4zf-0000or-Pg for pgsql-hackers@arkaria.postgresql.org; Sat, 24 Jun 2023 15:16:07 +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 1qD4zf-0000oi-G2 for pgsql-hackers@lists.postgresql.org; Sat, 24 Jun 2023 15:16:07 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qD4zc-000Eaw-Pr for pgsql-hackers@lists.postgresql.org; Sat, 24 Jun 2023 15:16:06 +0000 Received: from [192.168.0.104] (unknown [62.217.185.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: p.luzanov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id C29A1E20E49; Sat, 24 Jun 2023 18:16:04 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1687619764; bh=DN56XCurtzrS9jCx4jVWFzdquZgFnXvCrr6KZZIIgfM=; h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To: From; b=BVGd4sbkIrvp/PfJv/HPfciNpr4NxMUdX+AZwnXphRKoIeEFXixvc/UNLKcIbc+T4 PIX7gA+bexLjN0vliit5n7bDAI0JauU88AO4Gjpo7ZsBdFb36DFUWFBntE8AqX2YpH XI4Yb9AO6hnuhwkkXMCQ4EeD5AVuzbnjzksFmzApGMA23aH4RiUilcO+bw6juZ4EYE BWyamyuMbH3NmBiXo5hpqWYodVVIsXnYDgQ/z3AW3IzUuywl7dls1ckknkL8fe+cD/ 7mED6roewBXm4BHK44O4UsFIy7vH/uOKqIMrtYLs1d6eMWEQP9l1tqpHR+f2aYSczS sQs1FUrrKcFQg== Message-ID: <5ab5b6c8-4eb2-c8d0-3521-8e5c5cb167c7@postgrespro.ru> Date: Sat, 24 Jun 2023 18:16:04 +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: Things I don't like about \du's "Attributes" column Content-Language: en-US, ru-RU To: Tom Lane , pgsql-hackers@lists.postgresql.org References: <4133242.1687481416@sss.pgh.pa.us> From: Pavel Luzanov In-Reply-To: <4133242.1687481416@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 23.06.2023 03:50, Tom Lane wrote: > Nearby I dissed psql's \du command for its incoherent "Attributes" > column [1]. It's too late to think about changing that for v16, > but here's some things I think we should consider for v17: If there are no others willing, I am ready 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