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 1nMhY6-0002pX-EF for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 02:38:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nMhY5-0005lW-6j for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 02:38:37 +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 1nMhY4-0005lN-PC for pgsql-hackers@lists.postgresql.org; Wed, 23 Feb 2022 02:38:36 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nMhY0-0001oP-Cz for pgsql-hackers@lists.postgresql.org; Wed, 23 Feb 2022 02:38:36 +0000 Received: by mail-il1-x12a.google.com with SMTP id d3so14198392ilr.10 for ; Tue, 22 Feb 2022 18:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=M1d8T3hHuWmVzqOyxVe6N4AjX4nuy9WdUOp+ONCIpd4=; b=lLBvDDTKpRpF34gHWsPYo9ZG88r27+A3RxR0Hm5u+wiALoo9eS6TQvFfOTrmZuAOlH eHxL48WPgll6uIspT1hEDcU6DANV58/wQmD7wL/0M8UX+B69w+Fp6SeYzWbRWQQT9FpC BPi9Ph3cDKBUAugOhyHV+2qiiJsfryeM/zTbPhWufP724sN6u7kEM9MZzqesxrsuzzAx JAj3+b6G824rPrf1Cg87REdT47w/ImqCDhbhnEFqk7tvyLC2YmCk8rwDiB9usnI5pDq2 eEmOAxaJwUlDVYzfaZycm4VejTJSViQPumLnuTKzGwLmmCl4aYI2R85nmfWu6zCvUE9I qXuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=M1d8T3hHuWmVzqOyxVe6N4AjX4nuy9WdUOp+ONCIpd4=; b=si/aTlwErYmAAcQOwJ2PWrAn2wT9i3c+1D83JsNIhhyn7k9jAvxdK77otkJkJ83kCD 2zlxb2wsBSVEmxWBAvHrRVuadxhpWAi+pd5V0cAFbbapSxOiSSe0eIq2Wra244nWtdP1 WKI+s23pAEiq0Q3xJOSYOe0XmMmE1zw/f8nUUHQwntZ7Mmhyuf7BvFMnmbdwt6HJCg78 k8x6lZ8VSyxInhR3gYL5hffh7qEw6CaC6O8JR2A+FFKckkPN4Inv/ZwFPDKhtpM2aHLO 0Oj9qZvmVI7x6H+rUbiMLp8P6xyBbveclqX5rRMNuz0muLzrGnmj+u9D/ZQzGrfdb4h1 aLbQ== X-Gm-Message-State: AOAM5339NDR8Nf5plXDE7MZwMU18TT7NOzFfyAfFDdJNiTUwOqGbPYOY GSxnwhpr/uQio9nXbe9QfOWm8xztjdghrg== X-Google-Smtp-Source: ABdhPJyU8sVVa9zcVVcoNADQpPABWx+4BX1QV/s1aNrTHXavqs2bLRtRLsRWOVUoj9R+bT2W4w+abw== X-Received: by 2002:a05:6e02:1d8e:b0:2c2:7c28:3daf with SMTP id h14-20020a056e021d8e00b002c27c283dafmr166684ila.314.1645583910424; Tue, 22 Feb 2022 18:38:30 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id s10sm5915999ilt.20.2022.02.22.18.38.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Feb 2022 18:38:30 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id D05B8800612; Tue, 22 Feb 2022 20:38:28 -0600 (CST) Date: Tue, 22 Feb 2022 20:38:28 -0600 From: Justin Pryzby To: Michael Paquier Cc: Julien Rouhaud , pgsql-hackers@lists.postgresql.org, Bruce Momjian Subject: Re: shared_preload_libraries = 'pg_stat_statements' failing with installcheck (compute_query_id = auto) Message-ID: <20220223023828.GK9008@telsasoft.com> References: <20220208034815.m4cwlyimmfjtgvoq@jrouhaud> <20220218093856.zenl2axicm5mmdc5@jrouhaud> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Feb 22, 2022 at 11:04:16AM +0900, Michael Paquier wrote: > On Fri, Feb 18, 2022 at 05:38:56PM +0800, Julien Rouhaud wrote: > > On Fri, Feb 18, 2022 at 05:22:36PM +0900, Michael Paquier wrote: > >> So, I have been looking at this problem, and I don't see a problem in > >> doing something like the attached, where we add a "regress" mode to > >> compute_query_id that is a synonym of "auto". Or, in short, we have > >> the default of letting a module decide if a query ID can be computed > >> or not, at the exception that we hide its result in EXPLAIN outputs. > Okay, thanks. I have worked on that today and applied the patch down While rebasing, I noticed that this patch does part of what I added in another thread. https://commitfest.postgresql.org/37/3409/ | explain_regress, explain(MACHINE), and default to explain(BUFFERS) - if (es->verbose && plannedstmt->queryId != UINT64CONST(0)) + if (es->verbose && plannedstmt->queryId != UINT64CONST(0) && es->machine) { /* * Output the queryid as an int64 rather than a uint64 so we match Apparently, I first wrote this two years ago today. -- Justin