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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1qIqfF-00006k-3P
	for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Jul 2023 13:10:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1qIqfD-0003tH-SF
	for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Jul 2023 13:10:51 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <p.luzanov@postgrespro.ru>)
	id 1qIqfD-0003t7-Eo
	for pgsql-hackers@lists.postgresql.org; Mon, 10 Jul 2023 13:10:51 +0000
Received: from mail.postgrespro.ru ([93.174.131.139])
	by makus.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <p.luzanov@postgrespro.ru>)
	id 1qIqf9-0034kz-VJ
	for pgsql-hackers@lists.postgresql.org; Mon, 10 Jul 2023 13:10:50 +0000
Received: from [192.168.28.133] (unknown [192.168.28.133])
	(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 84DF3E20C32;
	Mon, 10 Jul 2023 16:10:45 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru;
	s=mx2023; t=1688994645;
	bh=O1mNujboQ5WF+5YCREs2CbWCeq6U8pdPVtecQBpmSyU=;
	h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To:
	 From;
	b=jI4lxnOyEg8pxtt47GhRoi4+bC2e+EOJ1gUl3rh6xen7SYtHqMDdvVsqEdzpQvsgS
	 Uvl2Hdchl8qdDK1QL8Z4rj/zydmBPaYFm5kYimo9xwGADWq8zrmL7vtBbjeRNqVLcV
	 GczzIJy9DYSKhwaPT7v2W4T/5rx8M3/+NGQQnzLvAxNnArzyZYXukUMj/nQX1gl7L5
	 ik2uHvWqg/Mre3h63XVRtYNKZlh2vGW9y222xJZc7eB1EXPnS38LnUqRdoVzKgoRs7
	 /rFVaglZYRfgHd5SJPTPnn6oec5SLXWnC0VBMOSvQ5Tw311gzecHfyAgC+RC8um+hd
	 TGlkap8E3dMgQ==
Message-ID: <7673aab4-1b93-00f1-2c62-b35008a190fa@postgrespro.ru>
Date: Mon, 10 Jul 2023 16:10:45 +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 <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
References: <4133242.1687481416@sss.pgh.pa.us>
From: Pavel Luzanov <p.luzanov@postgrespro.ru>
In-Reply-To: <4133242.1687481416@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/7673aab4-1b93-00f1-2c62-b35008a190fa%40postgrespro.ru>
Precedence: bulk

On 23.06.2023 03:50, Tom Lane wrote:
> * On a purely presentation level, how did we possibly arrive
> at the idea that the connection-limit and valid-until properties
> deserve their own lines in the Attributes column while the other
> properties are comma-separated?  That makes no sense whatsoever,
> nor does it look nice in \x display format.

I think this a reason why footer property explicitly disabled in the output.
As part of reworking footer should be enabled, as it worked for other 
meta-commands.

Just to don't forget.

-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com