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 1kCmVd-0003uY-Sl for pgsql-hackers@arkaria.postgresql.org; Mon, 31 Aug 2020 16:18:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kCmVc-0001aR-Qr for pgsql-hackers@arkaria.postgresql.org; Mon, 31 Aug 2020 16:18:16 +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 1kCmVc-0001aK-KG for pgsql-hackers@lists.postgresql.org; Mon, 31 Aug 2020 16:18:16 +0000 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kCmVa-0002YK-6S for pgsql-hackers@lists.postgresql.org; Mon, 31 Aug 2020 16:18:16 +0000 Received: by mail-qk1-x741.google.com with SMTP id w186so6667367qkd.1 for ; Mon, 31 Aug 2020 09:18:14 -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=4hKPM/4mkkd/2FmZP2mCV8cy/Mvpv9beTuT7WXGsfnc=; b=H/xbI/2U929IhlOst0Z6QeC6HRwK8+ZgHsNGNT+Rlyksx+Qn3ArlZu6cuODSCCWM6o aMZk8xxwrACGb1+1JgxSZqJMWzY+wvMy+o3v9jDSJuhQW6wseT6ISx3EI53U8x5As3fd eN5VOSc9dmP24g10Abt6yX0Pji366T2pXV14xeJ1aInu60KXMTpqy1jX30sZ9rLCcn6r 6GieNJqaHTJ8rZKwsODrZnIPxLOvHjx0hPnltOlowJ9cgEyA//ovsb1ptZRQ2vqSdkVv I5O/J212RkuEHUf47ZVgShy9eaLhnhzItSxGkBTZPa8akyGVzEwccc8go6KO+0NL065n 80pQ== 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=4hKPM/4mkkd/2FmZP2mCV8cy/Mvpv9beTuT7WXGsfnc=; b=UzqqA/o6kRCIipih5MgpnNciWFzjPUtxvzp7sOzBtp6HMMiirljUXOVxX8v/frsGa6 WT7Fz8CqcBeLcxt5xUVDue8Iz7CEjNd3k17ylxEd0sUndWuIWWPpK8tzbr1jsao9so5s 9QaHjEvs0Y9nIfYe8PFZEqcrKop061IensQvynhM26OF4jBqpF7Y0ejHXPHm+2vvShA9 ExiBJgmUcnPnB9JIAFSdP42Bxn4l1+5jDbsBhkaNbynt4tOMcJSseJkkLxna/c2lKTt1 iEJEAH69f0qjsMfITVPTD5NgUijrov0AVCLBrEyvYt79MW7/bSjM1ucIECwTUJesk1FR mgcw== X-Gm-Message-State: AOAM5332nFVPdc+i45PXUzu9JHSj8aS8C5sNJNZ65N6kr1xLQObaNhPs Fz3nQdDRXF0QzKs+8TZOhBKzkQ== X-Google-Smtp-Source: ABdhPJxl1fR6NDkK07HV8K5Rd6/KvX2E/G9NzIMjQEo38gnQpZUMXg/faOTsWV4Q1un1TWCNUB1H/Q== X-Received: by 2002:a05:620a:7ee:: with SMTP id k14mr2152927qkk.500.1598890692411; Mon, 31 Aug 2020 09:18:12 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.19.47]) by smtp.gmail.com with ESMTPSA id b43sm4538346qtk.84.2020.08.31.09.18.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Aug 2020 09:18:11 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id A8D9D2A0EF6; Mon, 31 Aug 2020 12:18:09 -0400 (-04) Date: Mon, 31 Aug 2020 12:18:09 -0400 From: Alvaro Herrera To: Tomas Vondra Cc: Tatsuro Yamada , Julien Rouhaud , Pavel Stehule , PostgreSQL Hackers Subject: Re: list of extended statistics on psql Message-ID: <20200831161809.GA31337@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200831153053.a343pjgumahiejhw@development> 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-Aug-31, Tomas Vondra wrote: > I wonder if trying to list info about all stats from the statistics > object in a single line is necessary. Maybe we should split the info > into one line per statistics, so for example > > CREATE STATISTICS s (mcv, ndistinct, dependencies) ON ... > > would result in three lines in the \dX output. The statistics name would > identify which lines belong together, but other than that the pieces are > mostly independent. Yeah, that's what I'm suggesting. I don't think we need to repeat the name/definition for each line though. It might be useful to know how does pspg show a single entry that's split in three lines, though. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services