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 1jnp6p-0004vo-J0 for pgsql-docs@arkaria.postgresql.org; Tue, 23 Jun 2020 20:01:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jnp6o-0005KA-GH for pgsql-docs@arkaria.postgresql.org; Tue, 23 Jun 2020 20:01:30 +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 ) id 1jnp6o-0005K2-78 for pgsql-docs@lists.postgresql.org; Tue, 23 Jun 2020 20:01:30 +0000 Received: from mail-qt1-x833.google.com ([2607:f8b0:4864:20::833]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jnp6m-0007DU-1R for pgsql-docs@lists.postgresql.org; Tue, 23 Jun 2020 20:01:29 +0000 Received: by mail-qt1-x833.google.com with SMTP id x62so13051177qtd.3 for ; Tue, 23 Jun 2020 13:01:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=UzEcv6URgr1bLl4RUtPXFWx0kZHSLl0OE3eD6Pbcnvo=; b=IH+59mTF3nE0jxiOVHlQhUxuPsr5vUh1KFHmajW/fATSXAcunUAMVhMNqS8sI9uyQx 26iYPiKleLY/9A6HX75tPEhZRmpqjWkd6S1JqlIuIA0pnDRmW6qVEWVNW0QX02jURm/R Jdk9sLzwajedAEAUlCefaXAkqNtbKMTsPNFXc7pBjSKxZ3PV3lPu3RWo990qLmxXHU+J H1WaWyVsMV0eFZ+gefq4Ml4K0AoE+TtQzWRhVuJpGzqgna/+T4PMJ5BeRWYStXsmw5hl 1WHA8P4ay4I05dMvPcEn6WTksUa/tuLh6StlD3348sTwxSCqciDa7sBTQlkw3pGs14mC ZZwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=UzEcv6URgr1bLl4RUtPXFWx0kZHSLl0OE3eD6Pbcnvo=; b=D4lUtKPfpYdKiSq4sFJVWdFdJwZOPKHDQYx6zvQUjb5/Q0OrIQI6wE1WgSrlve98zN A3q4BNwLhzrvbrDuy7B0NZV01Hd5BaHfI9q6EKLbEHzQ0F05zeTLdEaD3b9kMzE9Ey5p 95m+w06e2te95hbUoelebhfC3NN/9q3ZWsFE7uRiyMPm6h4yYbXQHqx/+V3dzDB+tmZd Fj+f+kYiZT/vN0dQ1+Pb46oLQ3ozx3KQmcWLMq6xVHILbgBaruFMOIW3Pov6lkrpbmJ2 rVjML22P/62sX/IPwqJdyfL+ElIQg+IxpsLqqZRaKNMU2qBuXwHyJLt2NTzIfFs4o7vm yWNw== X-Gm-Message-State: AOAM5326R/K5TCNelSX+y05B/OEDMNscItCBsIx/SqG+zuVms1De5kaH 2iM+Q+RNMPIc1WMQjKPvzXls5g== X-Google-Smtp-Source: ABdhPJyURXdG9wjo07OwQN0UIAyTeC94EuLrgmAhha9rDKJj+lapr4nK6aJFF29kupoWCnE3KpygtQ== X-Received: by 2002:aed:3fa5:: with SMTP id s34mr23634860qth.343.1592942487164; Tue, 23 Jun 2020 13:01:27 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id z3sm1399728qkl.111.2020.06.23.13.01.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Jun 2020 13:01:26 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1C8BD2A3A10; Tue, 23 Jun 2020 16:01:24 -0400 (-04) Date: Tue, 23 Jun 2020 16:01:24 -0400 From: Alvaro Herrera To: Steve Estes Cc: pgsql-docs@lists.postgresql.org Subject: Re: Summary of DDL/DML statement return/output values? Message-ID: <20200623200124.GA17686@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Jun-23, Steve Estes wrote: > Thanks Alvaro. Looks cool. So, on the one hand it'd be nice to be able to > auto-generate this once all the commands are standardized into one > structure. That'd be slick. I thought they were already standardized ... But anyway, I was thinking that this would generate *one* table listing all commands with their tags. I was not thinking in putting the tag in each command's page: I'm not sure that that would be generatable. > On the other hand, the number of commands in SQL is not that large a > universe, such that it'd be at least somewhat practical to just add Output > as a standard section of the doc page for any command. They number 182 in > both v11, v12 and v13 thus far, and many of those are variations of ALTER, > CREATE or DROP (127 of them, in fact), such that they probably mostly share > an output format. More importantly, the output of each command is unlikely > to change much going forward, certainly not within a major release > (right?). So we could just document each command's output, and if need be > then pull that information into a summary page thereafter, or when the > commit you mention is finished. I can't say I'm terribly excited about this idea. I won't stop you if you want to pursue it, but I'm not sure I see the value in a RETURN VALUE section that says that the command returns the command name. Maybe it would make sense to have that for the exceptional cases only? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services