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 1t8NUa-003oXT-7i for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 17:37:23 +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 1t8NUX-00GYMK-Lh for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Nov 2024 17:37:22 +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 1t8NUX-00GYLb-CT for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 17:37:21 +0000 Received: from mail-wr1-x42d.google.com ([2a00:1450:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t8NUV-000L5p-DQ for pgsql-hackers@lists.postgresql.org; Tue, 05 Nov 2024 17:37:20 +0000 Received: by mail-wr1-x42d.google.com with SMTP id ffacd0b85a97d-37d4fd00574so26084f8f.0 for ; Tue, 05 Nov 2024 09:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730828237; x=1731433037; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=b1e/QAB15mohmfqGV/SknwPaxRjL1AfrXOpvLB5sOZc=; b=PPaXyfALAcbpDAqXPc4QZYFKYqUZpqY2FpjCTvAfm1nPU0fk1rC/+hRd5QH0E/NgoR pTMy7/8w90RXFTgPLPnZTYKHlzU4usmgt0lM1DV00VEsaHafNGZUkYl3/Frsaltwgztb DQEBw6JRWHvs+jfu7lE1jjYMZF8aqtzQzS2fZEkYdu5Wbyxpwwj8zWs5FRH/u5aYM+WO HhyYYiRXHPEDZELe1R4Lks5Pu3qNm5uIxKKFMEdKkmFjIvP4uJQ9m7UG2QU5YPEc7ZUe H+SJKFf0O9tExkNoHvs/TSO1ky3rAumD8ZCbX/2SifNAq+I0HVOO9/w1ymZcNAdyzhP5 DduQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730828237; x=1731433037; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=b1e/QAB15mohmfqGV/SknwPaxRjL1AfrXOpvLB5sOZc=; b=XuKZeGVshyvmirGHMtsA7KxzvfXTWr1ErFEvk2uy5kGlYQnPljlVHQP1ptUp4UQzth IiPDb03K3FD+0uSgY0wktfGKh5+jBWUb+JI1g+em4e4+Ttex0zW9y9L6S9eH7YGtTHpX XnwHbh8+S8yXdHFjkJe+ACqfQCQxsKUBPH7jgYs4UAvcGya490xRKseuLam7en6R38of MCzK1V/iEL6/oLQq428EErw3zqg5Q3cxQfsqbihddaa1NE5wcw2t/wWkAzFahT9xVY8w iJxpFdxIk/Qro2ubwZhj93BYB889+R4TnCvKheqi2MyK58sWkAz1f085qP3TW/ybQfZc jUhQ== X-Forwarded-Encrypted: i=1; AJvYcCVPl59n39UjtxoDFRNRz//RQ81UsPbkGTkXOBw61eeQHQmYryMQalg+6EqanLKPzD1VbO4bIgCPgXZbkqt0@lists.postgresql.org X-Gm-Message-State: AOJu0YyM5GHhtuvh3dRCCKT4+Z43zATr6G+rU+IobF4NbtiD4HKGtusQ hivdCFSyqg+VIYUI0KfhsYd9Tz12AxeRoc4c/2ZX3ul/niiFB7Bk X-Google-Smtp-Source: AGHT+IEIOWdfdvC4MMZHCR7lAVYQpWEeMfwBI53RagNnXsygl/KCN4+R93UsjPpx/8boyVhdDmLwuw== X-Received: by 2002:a05:6000:1869:b0:374:c6b6:c656 with SMTP id ffacd0b85a97d-381c14c3469mr18846236f8f.21.1730828236883; Tue, 05 Nov 2024 09:37:16 -0800 (PST) Received: from ip-10-97-1-34.eu-west-3.compute.internal (ec2-15-236-134-5.eu-west-3.compute.amazonaws.com. [15.236.134.5]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-381c116abdasm16964891f8f.97.2024.11.05.09.37.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Nov 2024 09:37:16 -0800 (PST) Date: Tue, 5 Nov 2024 17:37:15 +0000 From: Bertrand Drouvot To: Michael Paquier Cc: Nazir Bilal Yavuz , Alvaro Herrera , Kyotaro Horiguchi , pgsql-hackers@lists.postgresql.org Subject: Re: per backend I/O statistics Message-ID: References: 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 Hi, On Mon, Nov 04, 2024 at 10:01:50AM +0000, Bertrand Drouvot wrote: > And why not add more per-backend stats in the future? (once the I/O part is done). > > I think that's one more reason to go with option 2 (and implementing a brand new > PGSTAT_KIND_BACKEND kind). I'm starting working on option 2, I think it will be easier to discuss with a patch proposal to look at. If in the meantime, one strongly disagree with option 2 (means implement a brand new PGSTAT_KIND_BACKEND and keep PGSTAT_KIND_IO), please let me know. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com