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 1t3aao-00DROn-WB for pgsql-admin@arkaria.postgresql.org; Wed, 23 Oct 2024 12:36:03 +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 1t3aan-009MDa-AK for pgsql-admin@arkaria.postgresql.org; Wed, 23 Oct 2024 12:36:01 +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 1t3aam-009MDE-Sc for pgsql-admin@lists.postgresql.org; Wed, 23 Oct 2024 12:36:01 +0000 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t3aag-002S8M-Id for pgsql-admin@lists.postgresql.org; Wed, 23 Oct 2024 12:35:59 +0000 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-43161c0068bso53904785e9.1 for ; Wed, 23 Oct 2024 05:35:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729686953; x=1730291753; 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=SQ+vaVXkb9CmjqcbvJgfPfBwqVjCKJaUqSLwdWhtLLY=; b=Kpi/8j84XnDZiHoktC6VOqo8p6wGYtbsHXm+xXYombdbj0WXDME/HMqUlQq3WDrsXX HyPFKaW7O3euEIOgot73ljZ0wEPlJWSr8mH23w0CFRqWnkoAUE911FhVfVgjqxaEdAb2 mgbkgaheimwhD6OrOAKjhUa26XqDdbkpVzKy4fjo0xdf9tj0stcrMUueZ/nZxkYaYu9K Ccygs6laI/ccQWzQMgBNnakIrFVc6byneW9Jn7SrDJIKz2XOHACLlB0w34QCvxAjsu2j ksmImRQtBkFr2xbg33vzMnHpNEuzGpIpPgfJRhs6JzSL3THMiUjJ+wMZt4TDaZ5P7jYg 55Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729686953; x=1730291753; 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=SQ+vaVXkb9CmjqcbvJgfPfBwqVjCKJaUqSLwdWhtLLY=; b=R7Z5rmtvbN5g6DbRFBCKHpRbuX2mSyd9wc0waKekUUwSZHKQ39Xlr35a9RNIeh0/tC V17q+nA1T6bwNOwsmL43YkwT0Ym1qTCTXxHQbgngYxl788plwmemdnvedbCwh14zdBJ1 bbn12eXCQApgvjjHmLc5Tox/0sL7Z0KRsBGaWRB7xv4hNTYMMnACXC2UHiccYyVUM3N/ AnM17S5MGcX7tv5AewaPAOZUV/fwQFx/C2oy9rwK6v6bnnTvFBdWnHkJTZv48OiFFcpN R5DliyVq8y76yQmMvKDIadF3L8BTZ2dWNij2ioH16mXnmzr7i3EQwalxXDTH1RntlSQU qDew== X-Gm-Message-State: AOJu0Yyq1w9bRkM7Aa/tWcefE9BcwCjT7ZU86OT5AAnnhLb6VPoNucDj /NSxiHRrOUVsxMy2sRaYpgeyICCJk1WEWskF5LVW7aBYryeQecPUdWAOqriGIgEkxMBo0/TsW5t +czYgWnxbvp409mIQb5Lq81VvCbQ= X-Google-Smtp-Source: AGHT+IHmCU8m7vaQ9R3SIqIN9GTFEikglc+vkVX/tH8L6DhtESWRWn77uzm0swSx9NcXrlZ8j1Pjc7WJ+qlHz0eVruo= X-Received: by 2002:a05:600c:3556:b0:42c:bae0:f065 with SMTP id 5b1f17b1804b1-431841e1786mr21128625e9.5.1729686952539; Wed, 23 Oct 2024 05:35:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: SOzcn Date: Wed, 23 Oct 2024 15:35:42 +0300 Message-ID: Subject: Re: Postgres capacity planning. To: Alex Balashov Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000006100d506252420e7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006100d506252420e7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I don't sure what you asking for but there is no any tool enough for the progresses. If you look some enterprise thing you can check pganalyze. PostgreSQL have enough monitoring extensions anyway. One of them is pgbadger, you can look at it. Have a nice day. Alex Balashov , 23 Eki 2024 =C3=87ar, 15:13 tari= hinde =C5=9Funu yazd=C4=B1: > > > On Oct 23, 2024, at 8:02=E2=80=AFam, Daulat wrot= e: > > > > Could anyone please suggest any freeware tools, scripts, or ideas for > creating a capacity planning solution for a PostgreSQL database? Thank yo= u. > > I suppose this is one of those areas where "knowing Postgres well" is the > idea, and it's unlikely that this can be replaced with a tool. > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com > Tel: +1-706-510-6800 > > > > --0000000000006100d506252420e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't sure what you asking for but there is no any t= ool enough for the progresses. If you look some enterprise thing you can ch= eck pganalyze. PostgreSQL have enough monitoring extensions anyway. One of = them is pgbadger, you can look at it.

Have a nice day.

Alex Balashov <abalasho= v@evaristesys.com>, 23 Eki 2024 =C3=87ar, 15:13 tarihinde =C5=9Funu = yazd=C4=B1:

> On Oct 23, 2024, at 8:02=E2=80=AFam, Daulat <daulat.dba@gmail.com> wrote:
>
> Could anyone please suggest any freeware tools, scripts, or ideas for = creating a capacity planning solution for a PostgreSQL database? Thank you.=

I suppose this is one of those areas where "knowing Postgres well"= ; is the idea, and it's unlikely that this can be replaced with a tool.=

--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800



--0000000000006100d506252420e7--