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 1jNOgq-0005tF-4a for pgsql-hackers@arkaria.postgresql.org; Sat, 11 Apr 2020 22:33:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jNOgp-0006kU-2b for pgsql-hackers@arkaria.postgresql.org; Sat, 11 Apr 2020 22:33:27 +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 1jNOgo-0006kN-PQ for pgsql-hackers@lists.postgresql.org; Sat, 11 Apr 2020 22:33:26 +0000 Received: from mail-qv1-xf41.google.com ([2607:f8b0:4864:20::f41]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jNOgl-0001Ye-F5 for pgsql-hackers@postgresql.org; Sat, 11 Apr 2020 22:33:25 +0000 Received: by mail-qv1-xf41.google.com with SMTP id du18so2267548qvb.4 for ; Sat, 11 Apr 2020 15:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Gnq+Y3Txm8jlnnHRsCZN3Y3PNuqCsaVzasussMIs+Tw=; b=b498PHKA8lF6gJtlt4s/GzFXOwrxC8bzUPKd7VCuC9ggjUWjWfUYhgn2rFsLIJQwh2 TSJFQMZLRZK30XSd5fZXg2EXuDfSsQYZyKbhQivmd/uxkfOpTn70shK5CSbFbDgD4/YN YSX839xPCALGl9Evu5nvts44U3CD25ls8aefET4gBb6SHX75RJ0YxNcUo4wfvlC6KmSo ZGh/US9Y8QeEiJNTG1PAcnI5sxpG+5zrP3ECG0P1tnso4HtMsid/CUlkib2gAMQB+8w6 DqGhMmctCOcTlkDv+EtD0/Yg1dMVwI6XkRqlqq1vz7qVtN6KJBJtXV4jEOcWS1sCRGny 8CBw== 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:user-agent; bh=Gnq+Y3Txm8jlnnHRsCZN3Y3PNuqCsaVzasussMIs+Tw=; b=qcXDwgu8iaJ3kS70D1YH7GX5C5+HyadobrVziXFE8MT775fClLgFQGYSrgqZTrTWAe POb84AJUtrX6y0HMlplEYxl11wvEvNpSubauBAhiGok9xudO6GkwbXCU43bHqHVJEeEF HSDGJDc/iaNoVBrVb/s0CKiSFX+irOQRLCvZNuNaKef9Kt+IdVDsAwAmEdgMfI1cemkY Z8DrGAHQUmGXKGlhMU5FvbvOA1GQJ88TCrInUPUpCeAdzrfahRA8nrkWWn9qasrbaPo3 9GfS+NtKxkdZJJSpr28BxB443h7hYEiKU5RpCNG3asNeo7k1WUpzZLOOsrjwpXsUmddG mlfw== X-Gm-Message-State: AGi0PubHoCcKUxHwAiuXYeeC/MiEJjoUOsDm9wT8FeXiDFP+14KGxAU4 BqaoWkrmVqOd/klsTme5IoK72g== X-Google-Smtp-Source: APiQypLsKY70HUnzASvERN9Wh5/002et0MW3zHLEx/BD7vzkQTByxhUMZVAqWzRfgmspD3WzAnvJGw== X-Received: by 2002:a0c:f806:: with SMTP id r6mr10568933qvn.24.1586644402006; Sat, 11 Apr 2020 15:33:22 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id m1sm4778029qtm.22.2020.04.11.15.33.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Apr 2020 15:33:21 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id DB7BA800AE5; Sat, 11 Apr 2020 17:33:19 -0500 (CDT) Date: Sat, 11 Apr 2020 17:33:19 -0500 From: Justin Pryzby To: Julien Rouhaud Cc: Amit Kapila , robertmhaas@gmail.com, pgsql-hackers@postgresql.org Subject: Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch) Message-ID: <20200411223319.GM2228@telsasoft.com> References: <20200319153129.GA36079@nol> <762d4ee8-9710-cdcd-e661-b5c79aaa9bf0@oss.nttdata.com> <20200328133827.GA12854@nol> <20200328151721.GB12854@nol> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200328151721.GB12854@nol> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, Mar 28, 2020 at 04:17:21PM +0100, Julien Rouhaud wrote: > On Sat, Mar 28, 2020 at 02:38:27PM +0100, Julien Rouhaud wrote: > > On Sat, Mar 28, 2020 at 04:14:04PM +0530, Amit Kapila wrote: > > > > > > I see some basic problems with the patch. The way it tries to compute > > > WAL usage for parallel stuff doesn't seem right to me. Can you share > > > or point me to any test done where we have computed WAL for parallel > > > operations like Parallel Vacuum or Parallel Create Index? > > > > Ah, that's indeed a good point and AFAICT WAL records from parallel utility > > workers won't be accounted for. That being said, I think that an argument > > could be made that proper infrastructure should have been added in the original > > parallel utility patches, as pg_stat_statement is already broken wrt. buffer > > usage in parallel utility, unless I'm missing something. > > Just to be sure I did a quick test with pg_stat_statements behavior using > parallel/non-parallel CREATE INDEX and VACUUM, and unsurprisingly buffer usage > doesn't reflect parallel workers' activity. > > I added an open for that, and adding Robert in Cc as 9da0cc352 is the first > commit adding parallel maintenance. I believe this is resolved for parallel vacuum in master and parallel create index back to PG11. I marked this as closed. https://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=34802&oldid=34781 -- Justin