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 1sp1gl-00FkcI-UI for pgsql-general@arkaria.postgresql.org; Fri, 13 Sep 2024 08:30:02 +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 1sp1gl-00Fwdn-AR for pgsql-general@arkaria.postgresql.org; Fri, 13 Sep 2024 08:29:59 +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 1sp1gk-00Fwbv-OR for pgsql-general@lists.postgresql.org; Fri, 13 Sep 2024 08:29:58 +0000 Received: from forward100a.mail.yandex.net ([2a02:6b8:c0e:500:1:45:d181:d100]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sp1gf-000w10-NP for pgsql-general@lists.postgresql.org; Fri, 13 Sep 2024 08:29:57 +0000 Received: from mail-nwsmtp-mxback-production-main-79.vla.yp-c.yandex.net (mail-nwsmtp-mxback-production-main-79.vla.yp-c.yandex.net [IPv6:2a02:6b8:c29:f5dd:0:640:c3d2:0]) by forward100a.mail.yandex.net (Yandex) with ESMTPS id 4EBC5470B7 for ; Fri, 13 Sep 2024 11:29:49 +0300 (MSK) Received: from mail.yandex.com.tr (2a02:6b8:c15:2a18:0:640:9da8:0 [2a02:6b8:c15:2a18:0:640:9da8:0]) by mail-nwsmtp-mxback-production-main-79.vla.yp-c.yandex.net (mxback/Yandex) with HTTPS id kTg7R44O5eA0-WA9whIZI; Fri, 13 Sep 2024 11:29:49 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=primeit.com.tr; s=mail; t=1726216189; bh=vNL1cJFHSqWbSZ3BlF92OD3jtusQ3WyovhZ7AohF7jQ=; h=Message-Id:Date:Subject:To:From; b=FJmioLdlk4LBOs6vZzacXbDVlZM8Q+gZPIGSxQsDpY4dyiwqoUPvtiYRjqJsN+O0/ G74mgq0bNkkMbuIGnRqAlxPfBJtR6TXrIR/MknkpldTr2bPXfKW7NYVpR8QZ/Ia8cR q1GNxkNANSnVX/p3ExqXKOKOhO2kX9k5wEtHY1KM= Authentication-Results: mail-nwsmtp-mxback-production-main-79.vla.yp-c.yandex.net; dkim=pass header.i=@primeit.com.tr Received: by 3drt7umvdrfhvfn2.vla.yp-c.yandex.net with HTTP; Fri, 13 Sep 2024 11:29:48 +0300 From: =?utf-8?B?RWJ1YmVraXIgQsO8ecO8a3Rvc3Vu?= To: "pgsql-general@lists.postgresql.org" Subject: Storing plans with pg_stat_statements MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 13 Sep 2024 11:29:48 +0300 Message-Id: <373111726215371@mail.yandex.com.tr> Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk
Hello community,
 
As you know, pg_stat_statements is very popular and useful extension used by many Postgres user. What do you think of adding to store or capture also query plans as new feature in this extension? This would be an optional feature by default closed controling with a parameter maybe. I am sure it would be very helpful feature for many of us.
 
I just present this idea for your consideration.
 
İyi çalışmalar
Best Regards