Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1twuT2-000uRi-Lo for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Mar 2025 02:56:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1twuT0-00E321-Rb for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Mar 2025 02:56:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1twuT0-00E31s-9b for pgsql-hackers@lists.postgresql.org; Tue, 25 Mar 2025 02:56:38 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1twuSy-000xvt-1w for pgsql-hackers@lists.postgresql.org; Tue, 25 Mar 2025 02:56:37 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 52P2uUtw1192186; Mon, 24 Mar 2025 22:56:30 -0400 From: Tom Lane To: Sami Imseih cc: Michael Paquier , Christoph Berg , PostgreSQL Hackers , ma lz Subject: Re: query_id: jumble names of temp tables for better pg_stat_statement UX In-reply-to: References: <1831838.1742656359@sss.pgh.pa.us> <80506.1742660683@sss.pgh.pa.us> <461405.1742691859@sss.pgh.pa.us> <1189112.1742869660@sss.pgh.pa.us> Comments: In-reply-to Sami Imseih message dated "Mon, 24 Mar 2025 21:38:35 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1192184.1742871390.1@sss.pgh.pa.us> Date: Mon, 24 Mar 2025 22:56:30 -0400 Message-ID: <1192185.1742871390@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Sami Imseih writes: > I agree that some may want stats to merge for the same tables, > and others may not. I will suggest this with some hesitation, but why not > make this behavior configurable via a GUC? > We recently introduced query_id_squash_values for controlling > the merge of an IN list, maybe this is another queryId behavior we should > provide a configuration for? I don't like that GUC and I would not like this one either. We learned years ago that GUCs that change query semantics are a bad idea, but apparently now we have hackers who need to relearn that lesson the hard way. (Admittedly, this isn't quite *query* semantics, which perhaps lessens the blast radius. But I think we're still going to regret query_id_squash_values.) regards, tom lane