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 1t3oM4-00EmmI-RO for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2024 03:17:45 +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 1t3oM1-00GHT1-MV for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2024 03:17:42 +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 1t3oM1-00GHSj-5l for pgsql-admin@lists.postgresql.org; Thu, 24 Oct 2024 03:17:41 +0000 Received: from mail-ot1-x32b.google.com ([2607:f8b0:4864:20::32b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t3oLx-002YDg-J9 for pgsql-admin@lists.postgresql.org; Thu, 24 Oct 2024 03:17:39 +0000 Received: by mail-ot1-x32b.google.com with SMTP id 46e09a7af769-7180f2f5fb0so259380a34.1 for ; Wed, 23 Oct 2024 20:17:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitnine-net.20230601.gappssmtp.com; s=20230601; t=1729739856; x=1730344656; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Ism/tI408AiD8hC74yo3nl8z+M+2/WC8dL/ErCep30c=; b=Bpbz2dhyCPZ2lGGkBJRkp2rI66IrbpQ2t/QwrVdQJTV7JiZSSUxGVpirzLLU2ctucH ERTQrJNgx13zny+CgiZxLMK+xCm5h4h4v+dyfMVnCMsWjujWh5S8RgGSY5NQlfHHi9HH UspaM7dr7WYDZOEPLQYbGXu3iWFPPsOdESSf2X4MhV4h7UJCz0EI2ZDMmLVNQLPm+1ug GNlAre0OtZAWvOHRjZcOB2H2gJMfwmiOpZMtNRzpmgqvby2hqIiWOzWepmQpsAgmRSAq JEYK0a81oMHMB9HeQk6mcgYh7jlTRdB04q6I7fYk1MEyhnjG7J9fMpZZeunavV1GVqCr OipA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729739856; x=1730344656; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Ism/tI408AiD8hC74yo3nl8z+M+2/WC8dL/ErCep30c=; b=b56/5jlokDm8JvoR0UAPqtcLIM8SNBTfzHo2lHhK96vT10qf1ntclHYoRZn9hustNr LJ1wEXtyecPh1kqVAQsmPGc7zaot0mEAXfbL5tVtnjWzt0KK8NUNA9yKQJhlRA0gieXi qhn2Bzcy/WymSvplcFOVenftcK6GOS/ka+jbF6VIereMfqfITwHJceoexVG6qKQWsk+g gaJ6wAlVwsand9J4602cBtNg7UlyFJ/knjcrzGzWX42X60Dkzc510HVXRdcIruSk1R9m LSYdyalOfM1Krjub9dH+COqcMNDdM73gFKcEXW1d5xPSNYzej+/t7WdO1hniz20OGAGJ sODQ== X-Gm-Message-State: AOJu0Yw8wKT47cG6eDXnjYP5t1EajkJq+2tK83dJDM9V7lymAYCn/fQ1 QoUt0DrS9JrLh+P5FBm8gcYC/Z55oAP4XkzIqSB+BoJ2EdFa0KBS7XfkZux4J9eNZM5uITuDSd5 gq300kciuwl6UbBxjsZAwfY7VLJzLB5cv+NABYGITmPgyqdQqm0M= X-Google-Smtp-Source: AGHT+IHaYZEoz9dWWyu6d1e5I7OYbkPcZ2XRhYKFwb4t2PEUUDj1znMJijhD1hICb2NFK/+rEyF8jEiZddolej3C60s= X-Received: by 2002:a05:6870:3320:b0:288:64a4:fbea with SMTP id 586e51a60fabf-28ccb6a67damr4340727fac.42.1729739856282; Wed, 23 Oct 2024 20:17:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Usman Khan Date: Thu, 24 Oct 2024 08:17:24 +0500 Message-ID: Subject: Re: Postgres capacity planning. To: Daulat Cc: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000b0234506253071c6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b0234506253071c6 Content-Type: text/plain; charset="UTF-8" Hi, For PostgreSQL capacity planning, you can explore several freeware tools and approaches that help monitor and forecast database resource utilization. Some of the approaches are as follows: * pgmetrics: A tool used to collects and reports PostgreSQL metrics such as database size, table sizes, buffer cache utilization, index usage etc * pg_stat_statements: Tracks execution statistics for all SQL queries * pgCluu: It provides detailed reports and charts based on system statistics and PostgreSQL performance. * you can use the combination of Prometheus and Grafana * Pgbadger: It generates performance reports based on log files. On Wed, 23 Oct 2024 at 17:02, Daulat wrote: > Hello Everyone. > > Could anyone please suggest any freeware tools, scripts, or ideas for > creating a capacity planning solution for a PostgreSQL database? Thank you. > > > --000000000000b0234506253071c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

For Postgr= eSQL capacity planning, you can explore several freeware tools and approach= es that help monitor and forecast database resource utilization. Some of th= e approaches are as follows:
* pgmetrics: A tool used to collects and re= ports PostgreSQL metrics such as database size, table sizes, buffer cache u= tilization, index usage etc
* pg_stat_statements: Tracks execution stati= stics for all SQL queries
* pgCluu: It provides detailed reports and cha= rts based on system statistics and PostgreSQL performance.
* you can use= the combination of Prometheus and Grafana
* Pgbadger: It generates perf= ormance reports based on log files.


On Wed, 23 O= ct 2024 at 17:02, Daulat <daulat= .dba@gmail.com> wrote:
Hello Everyone.

Could any= one please suggest any freeware tools, scripts, or ideas for creating a cap= acity planning solution for a PostgreSQL database? Thank you.

--000000000000b0234506253071c6--