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 1vtQ5s-006KFR-2V for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Feb 2026 12:58:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vtQ5r-007rS1-1Z for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Feb 2026 12:58:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vtQ5r-007rRs-04 for pgsql-hackers@lists.postgresql.org; Fri, 20 Feb 2026 12:58:51 +0000 Received: from mail-vk1-xa2a.google.com ([2607:f8b0:4864:20::a2a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vtQ5n-00000000Mjs-2zyw for pgsql-hackers@lists.postgresql.org; Fri, 20 Feb 2026 12:58:49 +0000 Received: by mail-vk1-xa2a.google.com with SMTP id 71dfb90a1353d-5663724e4daso1952131e0c.3 for ; Fri, 20 Feb 2026 04:58:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1771592328; x=1772197128; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=LFSf6HhvaE1yervWVJR8VEiil+OWZHHtUXgb1vRRz3g=; b=arBm8CGFI6TFiMROVGRxHVFJX/O/SvOrngM1cOttNMJe5yDOfMKPR3dDbbydBw4vUu Mx8ovusCPutSpsmgIBkLowwBhuXPxhN21Mp6vcbyaIVdsD5+C9ESuKj7JFcILgbUV0w1 KtxlrQQXmigXJBF0sBDN+qFXgN6v8rkHiRSSIq/TbzxCAnzDyoAJiv2yfB4qeIGP7IUn wnF3VJjhHCgZioKMBQ6s3dygqh6cMGgJoR99ye4ZuMLI+igO89buKsyg1JXNj2TuabjD 6ln6tDZw+MQU2KEOtM/xKcBRGPOBE5GxvHiiHCNvPtQ4MpdrDsXJ1xRK5VyC8El4STTE 3fXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771592328; x=1772197128; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LFSf6HhvaE1yervWVJR8VEiil+OWZHHtUXgb1vRRz3g=; b=pO90Ws/qniSzQ3+RY1Ys+V/s/QQkiQNOxSPeNApY8pSAp+t3Manw3JY1sYYyiMoakD e9BVZcLdB1Zw949RotynvQevcPvGUWGMSy0NnhrRx1Hh9D5Iy8mhiGGnL74NIZCk9Gk0 jLOs+H1rF/RU9/1FlmdWzodRSKrUc6C8VZGIUZ6DQ4s/l9v9WhfNm8cfafPWQmZ5/Gqw 6pBgi+ctVHGTSG4O2JaJWDsUljfW+rPNVcoYUpszILSIhE6R2UgDv0JM/d2kzYVGG8D7 P66H4xeN85PnfD9TKAtRaWxRRgC/hF2L2CFgYzq8fUFdQj67MpU6FVxOPVbHNcY7K0y3 y1gQ== X-Forwarded-Encrypted: i=1; AJvYcCUVKrv46XoOlneyWkTTl1lMEYI3Ik/e42OdKeRPrNSFS+ZjI4c3Vf74fUyx+DAQIelEosieikf4d0vmGutQ@lists.postgresql.org X-Gm-Message-State: AOJu0Yz4KZh/rJwQWaorwBSMZMAUibldbO/fTemUHzARLA0jFeNxDIEk ETgHoBRvWhUpLGo+OcMhCh17L+jXUvR+bcoIqlR2+lVa9K4QCHQV9B5z X-Gm-Gg: AZuq6aKrMS9Fspkyy3rgTKkrUV+4Ai7j3y4u6efrdRa/RRF3V1P1pcJs3Qy4HCqy+0I UToLGVYgs+YON8inZagEIeAx1PLQyqp854vZ3JABzpf4vCMS86qhLpZ+ctBgEmeLSlDB5D2huko oVTrehgrSmjGDUxf8M/3YuPr/O30EESuVt1frKH5GiCiUX8o3lDw0q5CZFdDtD8JHi+bZqo7a6V 5n1cyqeUL2i+pkOpCgh9kXpp315umxOf5VRqn0nEDmcVRnAA54OIaaISkg4zPsESJNkZIkLxnHT wJpB5SObN8b1VwmbQ/gmFWDm89CpTyDdKxRyx0MiYC0cfoljh3NG/fPFlJgOka3tHtTyM6230zn U5HeNNhneKj0ECN24a2Cg8MesRR9+IfKMwZDt+d9MEwyBG23sR5gSiZjl7ZznL0Wp1uR/bOK0pv QmL5tj5WhQcRXXutH3a7jeA8zNUDfEWOhn9AraIT35BwQD2A0urL84E39foW6Y7YIw3InTsxJm1 fCRxUA7cWWOr/YRK7s= X-Received: by 2002:a05:6122:3306:b0:567:3ac6:5a67 with SMTP id 71dfb90a1353d-568dce7648dmr800456e0c.15.1771592327923; Fri, 20 Feb 2026 04:58:47 -0800 (PST) Received: from ?IPV6:2804:14d:328a:a59c:300f:55a:7205:4458? ([2804:14d:328a:a59c:300f:55a:7205:4458]) by smtp.gmail.com with ESMTPSA id a1e0cc1a2514c-94afd1ad879sm16575955241.6.2026.02.20.04.58.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Feb 2026 04:58:47 -0800 (PST) Message-ID: <57917e97-c9df-4829-9b86-914b131023d3@gmail.com> Date: Fri, 20 Feb 2026 09:58:45 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Show comments in \dRp+, \dRs+, and \dX+ psql meta-commands To: Fujii Masao , PostgreSQL Hackers References: Content-Language: en-US From: Matheus Alcantara In-Reply-To: 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 Hi, On 16/02/26 11:57, Fujii Masao wrote: > Hi, > > The psql meta-commands that list publications, subscriptions, and extended > statistics (\dRp+, \dRs+, and \dX+) do not display their associated comments, > whereas other \d meta-commands do. This makes it inconvenient to view > these objects together with their descriptions. > > I'd like to propose the attached patch to improve \dRp+ and \dRs+ so > they include comments for publications and subscriptions. The patch also > extends the \dX meta-command to accept the + option, allowing comments > for extended statistics to be shown when requested. Thoughts? > Thanks for working on this. I miss the \dX+ feature when reviewing your other path on improving documentation for CREATE TABLE LIKE. The code seems correct to me and it's working as described, I don't any special comments. > BTW, while working on this, I also noticed that \dRs+ currently outputs nearly > all subscription parameter settings (for example, [1]), whereas other > \d meta-commands tend to show only a subset of details. So, as new parameters > (or columns in pg_subscription) are added, the number of columns in \dRs+ > will continue to grow, which could make the output harder to use. > I think it might be better to exclude parameter settings to keep > the output manageable. > > As just idea, it may be sufficient for \dRs+ to display commonly used > identifying information such as Conninfo and Description in addition to > the fields shown by \dRs (Name, Owner, Enabled, and Publication). > Other details (e.g., Failover) could still be viewed directly in > pg_subscription. > Thought? > Yeah, I agree that the output can will be harder to read when the number of parameters (or columns) in pg_subscription grow, but since most of these columns are visible only on verbose mode (+) it doesn't seems an issue IMHO. In the future if the output columns grow too much we can rethink this, but for now I think that it's fine. +1 for the patch. (I've reviewed the v2 attached by Jim on [1]) [1] https://www.postgresql.org/message-id/82b25785-0dc1-46d6-93ac-ce385a3a0bfc%40uni-muenster.de -- Matheus Alcantara EDB: https://www.enterprisedb.com