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 1vC4oa-008hVH-9d for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Oct 2025 23:33:51 +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 1vC4oZ-00CaMK-7u for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Oct 2025 23:33:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vC4oY-00CaMC-7N for pgsql-hackers@lists.postgresql.org; Thu, 23 Oct 2025 23:33:49 +0000 Received: from fhigh-b2-smtp.messagingengine.com ([202.12.124.153]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vC4oT-003tKG-24 for pgsql-hackers@lists.postgresql.org; Thu, 23 Oct 2025 23:33:48 +0000 Received: from phl-compute-12.internal (phl-compute-12.internal [10.202.2.52]) by mailfhigh.stl.internal (Postfix) with ESMTP id 9AD9E7A00E4; Thu, 23 Oct 2025 19:33:42 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-12.internal (MEProxy); Thu, 23 Oct 2025 19:33:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1761262422; x=1761348822; bh=8GcIceJm4I 3AGDspYh8rInSQxYQQFJ2OGxT7n06fmQE=; b=WcSm+Yjv1a6oLRiMTgRPboW187 LAL8rCyQJ/LJxYPZdV4SmDB0V+4Hk6mwvzHffk3BiXM/a8BIAsTbjZdl3vcdfS7k O4OIWZDS7yKg0SQl0m6Sbx0VIhem7SeOBLrV6mErE0pa5h3ZWkjNO5Xw79TlFBG9 CtNyxmuo23o003KuESKK8fxjMDX80cZjM5i8uGNJLvWPNomkdeVkpKlrD4kWb9BK UacjGzUelzgihDPueGap1xHMRk1Q7htWoHZcgffJ7AxoVDYzMYH8Vz0EAfuOfrXR wxaAwqN+vpy+tUScLP+Ou4L3ft8fWiNIlUjmVGAQK4cqgXBqzLzzPWjsbXXQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1761262422; x=1761348822; bh=8GcIceJm4I3AGDspYh8rInSQxYQQFJ2OGxT 7n06fmQE=; b=AUaQ8clHJT9p4KAwF7M48b0uPCztxfe6GPb0QfcJ9B+3aam5nuB TewXUOVE+sOx2PUXQfWvbZ6UmGnYutSKoqTa7Wo6PGi4rngSukyV6jRs+Dl7bGly fgeCfywO0bzg2pkQasu3aa7bm/H1bEns2O1zTNLeOB1+KFF+ckAo+7Wxo+9zQzp0 DahxZG5n1ighuwhsbPp9TXtYVCEjIlHVSf7GdJc5RK9U36rZ+rC8ZshTKuA7ftcc Kd9WaF/lMXdgOG7Gic3rY8J8+0cAPxZqGwWlkIwm8hEk8vxiaECP83upwSg4/gkt UCjMI/BaujygH+SDVseCYO01bkTq5XDqKew== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddugeejjeelucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrh hlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeggeeg fffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiidp nhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepshgrmh himhhsvghihhesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhhrggtkhgv rhhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 23 Oct 2025 19:33:40 -0400 (EDT) Date: Fri, 24 Oct 2025 08:33:17 +0900 From: Michael Paquier To: Sami Imseih Cc: PostgreSQL Hackers Subject: Re: [Proposal] Adding callback support for custom statistics kinds Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PUinK6m7xdpmMUqV" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --PUinK6m7xdpmMUqV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 23, 2025 at 04:35:58PM -0500, Sami Imseih wrote: > Perhaps if someone wants to have separate files for each different > types of data, > we should be able to support multiple files. I think we can add an > option for the > number of files and they can then be named "pgstat..1.stat", > pgstat..2.stat", > etc. I rather avoid having the extension provide a set of files names. > So as arguments to the callback, besides the main file pointer ( as > you mention below), > we also provide the list of custom file pointers. >=20 > what do you think? My worry here is the lack of flexibility regarding stats that could be split depending on the objects whose data needs to be flushed. For example, stats split across multiple databases (like our good-old pre-v14 pgstats, but on a per-kind basis). So I don't think that we can really assume that the list of file names should be fixed when we begin the read/write process of the main pgstats file. -- Michael --PUinK6m7xdpmMUqV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmj6uz0ACgkQnvQgOdby QH1gmRAAjai8eklLbyOZF/gYL2plJ65d37YoM5E6ujTuOmsfkmXbS9tvMhDb/coy wVWKuiU6PF14s1F+F1r7eEOsYwEKnWIFCXfEGzhA3pu+kWIJx7rAGC1X+DFJ5bOo mBGeAHwMdxlP5otTs8zpx5gWNLodrLpdzfSi9qavQ7YZx5/oiSoWobW0TY+NXaEi V//BnyoGaRcEUJ4r1pFu+WV6XdvT5Lfoh6WcbIFmLO4nzAZTEmTdhHzkjPDqFjjr xsen4mTqSRS3iA2BaiqP4gTYJWm4s8E6hMQ7t0+vKAFJclFCk21QYhRd75Qg5H9h dK9dTXRGcqAaQ/+ooi6N4MtxR+viEvkJjEVQadILcUuAyJIAzR2uipj4ily992nA H77tBUevDM8aqikR4dmAc81HSWFJwOpvdnzUJ3queh/Bo7RpxBeGSAIiOFQcILfZ er4F8FLDM6NIfur58KITPPW6B4J09ZsamawRZVEV9eX7JA04EDUmJNXX8Ksr27d7 5wl3Fyx4Rmb9mNruUA2F83/y26O9FzuRhxRz8IzuRWxKRjerQXMVcank2sU+31Rm 7TU0Eq/c8/ZC5IVLrhioQYC9bnRu1dJ9VEb82OxzAsmoOfsAtNyA1sY4Y+afE9kn hHHaF1XYDVvE4/ufTbUyg8AZ8J3tER6d7kmJoJIEjV1v90ksFUo= =0g7W -----END PGP SIGNATURE----- --PUinK6m7xdpmMUqV--