Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvTR7-003kVK-30 for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Feb 2026 04:57:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vvTR6-009hmB-25 for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Feb 2026 04:57:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvTR6-009hlr-0h for pgsql-hackers@lists.postgresql.org; Thu, 26 Feb 2026 04:57:16 +0000 Received: from mail.postgrespro.ru ([93.174.132.70]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vvTR2-00000001KdZ-46q1 for pgsql-hackers@lists.postgresql.org; Thu, 26 Feb 2026 04:57:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1772081832; bh=7kJgwOILGwkSoOVreiPgJmSTEqnkZJqDKsZk3TAdyyU=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=d6/Gs+MkLQgaoTuT+XEKKdmdbeB6TSC1HF/GHsAh5h3t8aoRN3KGWJBPuVfNi69W7 vDdupmyHt7g5ebUz0KTNXDcHBL38iFfArI0Q9SHCV7AD78DceuLulD0LanL7rpTdfz gjUZ9+SiQDfosOOT8AFaC0RPRdO7f6UYon6AFmjP6BaCmeHFl41z8sVF+hNFX+gB3F OP9CugHN1AZyV/hZ2CtEYiKASSk2oVBiiunBnSsqfVWHLX0bqoy//DpwVrWv19FxQk 74KPNnUK85CZ5TLsUmXfRMK1zBFjYw/8IvRWBBF6yP+7atfqHyd/icGu4+00932xH/ Tk6xR/UGEYs1g== Received: from [192.168.43.15] (unknown [185.174.129.253]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: p.luzanov@postgrespro.ru) by mail.postgrespro.ru (Postfix/465) with ESMTPSA id A4E0E60B60; Thu, 26 Feb 2026 07:57:11 +0300 (MSK) Message-ID: Date: Thu, 26 Feb 2026 07:57:10 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Show comments in \dRp+, \dRs+, and \dX+ psql meta-commands To: =?UTF-8?Q?=C3=81lvaro_Herrera?= , Fujii Masao Cc: PostgreSQL Hackers References: <202602201522.fbznppk5cxmz@alvherre.pgsql> Content-Language: en-US, ru From: Pavel Luzanov In-Reply-To: <202602201522.fbznppk5cxmz@alvherre.pgsql> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-KSMG-AntiPhishing: NotDetected, bases: 2026/02/26 04:24:00 X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2026/02/26 02:02:00 #28225195 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 20.02.2026 18:48, Álvaro Herrera wrote: > So if you want details but > no comments, you use "\d+", and if you want comments but no details you > use "\d*", and if you want everything, then you use \d+* or \d*+? We need to keep in mind two more modifiers: S for system objects and x for eXtended mode. So it may be looks like slightly awkward: \dSx+* Another option is to use psql variable (for example ECHO_COMMENTS on/off) to force comments in \d* commands. I'm not sure what option is better. But I like the idea of printing comments. -- Pavel Luzanov Postgres Professional: https://postgrespro.com