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 1lgi4k-0007Ez-E5 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 May 2021 06:10:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lgi4j-0006lD-CI for pgsql-hackers@arkaria.postgresql.org; Wed, 12 May 2021 06:10:29 +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 1lgi4j-0006l5-2p for pgsql-hackers@lists.postgresql.org; Wed, 12 May 2021 06:10:29 +0000 Received: from mail-pj1-x1029.google.com ([2607:f8b0:4864:20::1029]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lgi4g-00053z-Cx for pgsql-hackers@lists.postgresql.org; Wed, 12 May 2021 06:10:28 +0000 Received: by mail-pj1-x1029.google.com with SMTP id g24so12956169pji.4 for ; Tue, 11 May 2021 23:10:25 -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=+Fd/F5zJDGCfJiTg1wO0/uiDXg/6KGNLdM+GO3yYv2g=; b=HyKuxDo85kBq1E1fcJEstTTaBa4Y3ykbIMEy+d7tuiIL52xdyQVOqOAobuvVYYTPBH cVRVIKUkbSkBLNLp5xzc6bpJ4SgCH2JJAkhnR0Ezh0KC9HtzVuHLEbHx3yHzA6TZFTo9 onwtX8O6JjL7huzsrR0D8pEP/eu8tehAGrTqkD5ygCWTNBmrZMP5m2C+QZRhd07OX51F Q/KVtN6MGE9Y7C+vqB1KiHBT+B/kvaFB83yY+Na72OubsjAX0Gtc+drmqB2jABwmruP0 VtJi5Jnf/y2LSv+jZVv25OXL7VvTWfuBZfsYnUp5oHp4WTHL/Q81G1S/H9FyU9H0g8sK ZlQg== 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=+Fd/F5zJDGCfJiTg1wO0/uiDXg/6KGNLdM+GO3yYv2g=; b=qlb2rP6WKd2qdEy781gNGIA7hGWqBwThFRElwvHtlh7SVFhn6DwBh1EUGTfOkFMZqQ pBLlBoYQSZRUy5esgj1Qh7/g0xActCRmguWmAeikUr1TjXFyvcLNRA1TA3bvFVdQbm3/ 6Lh6h3zjwBjymNiR+JfxKR180gNiPWo4kSODgmJ69z4EYlx3Ya1ZKfk8B9dcwJ4k3TOs wo7AblEDWlNfNQ/QCLmFSI284+TCtBlr7AKl1B+lSWJRKBa1LdtnXxW+9NqsIVN9COgF NTYvmJX2RkwVFoIOC63oAmGVvSr8WII+YIaRDCh5W6YO+IK7sbRBh9/mcxqadQKshBQ+ DYcA== X-Gm-Message-State: AOAM533+IQg2kl8mEfajse+AdXVpg4WhHXhYKiKqNonMkG4SiC/c8n1R 1c3l9d5zDoH+h/yw5Q6pzzo= X-Google-Smtp-Source: ABdhPJw6VwAGWn2iiGVbogA9FHW6w6wcsa8j2aQBG3qtWPpuY26RyLZQKIxcrAlRH+DPE8+DBz/j/A== X-Received: by 2002:a17:90b:1041:: with SMTP id gq1mr1412475pjb.75.1620799824462; Tue, 11 May 2021 23:10:24 -0700 (PDT) Received: from nol (2001-b011-0008-929a-d1b5-2d99-2ba7-4d91.dynamic-ip6.hinet.net. [2001:b011:8:929a:d1b5:2d99:2ba7:4d91]) by smtp.gmail.com with ESMTPSA id x10sm14978360pjq.53.2021.05.11.23.10.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 May 2021 23:10:24 -0700 (PDT) Date: Wed, 12 May 2021 14:10:49 +0800 From: Julien Rouhaud To: Pavel Stehule Cc: Kyotaro Horiguchi , Magnus Hagander , Fujii Masao , Michael Paquier , Andres Freund , Tom Lane , Alvaro Herrera , Stephen Frost , Bruce Momjian , Christoph Berg , Peter Eisentraut , PostgreSQL Hackers Subject: Re: compute_query_id and pg_stat_statements Message-ID: <20210512061049.dykngnivdoesquxb@nol> References: <20210511105249.2obdq32n6tc5gyqd@nol> <20210512.110836.2162399537656469720.horikyota.ntt@gmail.com> <20210512024201.ak3ofofakn2ymhiv@nol> <20210512.143335.1053382893089496881.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, May 12, 2021 at 07:49:13AM +0200, Pavel Stehule wrote: > > > Ah, I missed that case. And we are wanting to use pg_stat_statements > > with (almost) zero-config? How about the following behavior? > > > > > Until now, the pg_stat_statements was zero-config. So the change is not > user friendly. Apart from configuring shared_preload_libraries, but agreed. > The idea so pg_stat_statements requires enabled computed_query_id is not > good. There should be dependency only on the queryid column. I agree that requiring to change compute_query_id when you already added pg_stat_statements in shared_preload_libraries isn't good, and the patch I sent yesterday would fix that.