Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIpOy-0008VN-Ko for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Mar 2020 08:04:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIpOx-00076j-A6 for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Mar 2020 08:04:07 +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 1jIpOx-00076X-2l for pgsql-hackers@lists.postgresql.org; Mon, 30 Mar 2020 08:04:07 +0000 Received: from mail-lf1-x143.google.com ([2a00:1450:4864:20::143]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jIpOv-00034O-2d for pgsql-hackers@postgresql.org; Mon, 30 Mar 2020 08:04:06 +0000 Received: by mail-lf1-x143.google.com with SMTP id z23so13350079lfh.8 for ; Mon, 30 Mar 2020 01:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=L4293V8fevqrTCGLwsc4F+0vvTAGkwuGJJkv1cNWCEg=; b=EH4tfukao/x6ZLcxzyzdSwcK+8AYl+4iJgWIeWqMvAKjuuYqO2ZYVWXOvKL/+dOs7i usfQ9PSEkMccRlC8Mah/aT8xj27sNIpPEPWkGdnxXIduuTLVB53TP02FvPHzgALjmJGM 3ZuyLrnpeHdGIeQ3u5U5gUp11S4tlbxjQjCyxCwt6OASLnZzeKB/lE7o3gzITyeWMc3W yQe/Coa1s9isjaq60nQbaZtlMAqHTwAsqncqs085T0OkQNj09BdKOx+xF7lGhAGJL+12 hSAlHpVrn+XXvoQP7Ufa5WJNlNdJBIbSfxdqAIwcu0GmYdWkC7a6/RvJ0rWQt/g2yaWd PHMQ== 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:references :mime-version:content-disposition:in-reply-to; bh=L4293V8fevqrTCGLwsc4F+0vvTAGkwuGJJkv1cNWCEg=; b=PiKnsaIKzzaFR4lGIESsuRF+dYkA53CvezPp0NNKjJyeUFc6Dw7iZgu5phlvc5osXX e4gv++VXSP3HP2874hbhYfFCqiQuC08EaerTBHlaQrLlTQuzX4r84pyIQNVauMXnLzze ceAt7hrvjB3xDQ5sggALGF8OIfx1e89nhrdEch7hfYrK7eTklsxBF51IImXwF1R1Ok/Y V6ykhy+qunI4KYY/zRSnAopqCaE5SrpdmWj/FrG6wyzMKPZ96cZRAA2AoyOEI5SCZFyb 8LVPW4asi3hSgfkdTXYXxeG5SWpIo8tRaoiUkeo6CqEFLDOqBSJE8DjOJRHUeBw5UgVa g/8A== X-Gm-Message-State: AGi0PuZfpy6vUwuAyzgCSzqzmmOYXNQJE9yFX/V8w9JzFlmvZLfZXmC3 DkOQwIQlsJ95sTYgJLgwEaea/PkC6s0= X-Google-Smtp-Source: APiQypIFw+fyV5Oi6wdp/uMFvH1CxZwpHI1xZLGm15jNmUSCpyTJJfKxZpZA3yMxcd5bZIalWNb0DA== X-Received: by 2002:ac2:41d3:: with SMTP id d19mr7437803lfi.57.1585555444476; Mon, 30 Mar 2020 01:04:04 -0700 (PDT) Received: from nol (82-64-124-11.subs.proxad.net. [82.64.124.11]) by smtp.gmail.com with ESMTPSA id 28sm7310661lfp.8.2020.03.30.01.04.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Mar 2020 01:04:02 -0700 (PDT) Date: Mon, 30 Mar 2020 10:03:59 +0200 From: Julien Rouhaud To: Fujii Masao Cc: Sergei Kornilov , "imai.yoshikazu@fujitsu.com" , legrand legrand , "pgsql-hackers@postgresql.org" Subject: Re: Planning counters in pg_stat_statements (using pgss_store) Message-ID: <20200330080359.GD79261@nol> References: <20200320193004.rqgf3iim4fugq3sm@nol> <20200325134553.GA14054@nol> <20200326132242.GA80836@nol> <20200327100001.qarktrnxldmoxzgd@nol> <807c7d80-c748-3e86-d6e7-cfa01184ee92@oss.nttdata.com> <20200329061549.smtokn3ip5pqldia@nol> <8224bfdf-dcf8-648f-e0d8-1db1d5c215ee@oss.nttdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8224bfdf-dcf8-648f-e0d8-1db1d5c215ee@oss.nttdata.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Mar 30, 2020 at 01:56:43PM +0900, Fujii Masao wrote: > > > On 2020/03/29 15:15, Julien Rouhaud wrote: > > On Fri, Mar 27, 2020 at 03:42:50PM +0100, Julien Rouhaud wrote: > > > On Fri, Mar 27, 2020 at 2:01 PM Fujii Masao wrote: > > > > > > > > > > > So what I'd like to say is that the information that users are interested > > > > in would vary on each situation and case. At least for me it seems > > > > enough for pgss to report only the basic information. Then users > > > > can calculate to get the numbers (like total_time) they're interested in, > > > > from those basic information. > > > > > > > > But of course, I'd like to hear more opinions about this... > > > > > > +1 > > > > > > Unless someone chime in by tomorrow, I'll just drop the sum as it > > > seems less controversial and not a blocker in userland if users are > > > interested. > > > > Done in attached v11, with also the s/querytext/query_text/ discrepancy noted > > previously. > > Thanks for updating the patch! But I still think query_string is better > name because it's used in other several places, for the sake of consistency. You're absolutely right. That's what I actually wanted to do given your previous comment, but somehow managed to miss it, sorry about that and thanks for fixing. > So I changed the argument name that way and commit the 0001 patch. > If you think query_text is better, let's keep discussing this topic! > > Anyway many thanks for your great job! Thanks a lot! > > > > > > I also exported BufferUsageAccumDiff as mentioned previously, as it seems > > > > > clearner and will avoid future useless code churn, and run pgindent. > > > > > > > > Many thanks!! I'm thinking to commit this part separately. > > > > So I made that patch based on your patch. Attached. > > > > > > Thanks! It looks good to me. > > > > I also kept that part in a distinct commit for convenience. > > I also pushed 0002 patch. Thanks! > > I will review 0003 patch again. And thanks for that too :)