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.96) (envelope-from ) id 1wL2XE-001UGH-2G for pgsql-admin@arkaria.postgresql.org; Thu, 07 May 2026 17:29:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wL2XD-005J75-1l for pgsql-admin@arkaria.postgresql.org; Thu, 07 May 2026 17:29:15 +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.96) (envelope-from ) id 1wL2XD-005J6w-0P for pgsql-admin@lists.postgresql.org; Thu, 07 May 2026 17:29:15 +0000 Received: from mail-lj1-x234.google.com ([2a00:1450:4864:20::234]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wL2XA-000000012ki-3IjT for pgsql-admin@lists.postgresql.org; Thu, 07 May 2026 17:29:14 +0000 Received: by mail-lj1-x234.google.com with SMTP id 38308e7fff4ca-393925cb1baso11644591fa.0 for ; Thu, 07 May 2026 10:29:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1778174950; cv=none; d=google.com; s=arc-20240605; b=aHZA/UZ2wR7CjodCzkFf0Tc4TCM1mzLNqX2zb2NMd9PclQh2wjtMLzwDmWenBtflt3 FK7vpb8xtwazZnG6HSK/uPS6E2zfcpowKUQ29hBHhXdny/LOG/8PiA9sFDA3hlUtSc3P Hpi50P7WG77iSj9GOeW+mKSIS0QidRBd01RTXB+GpHFhGSFCqRdpTzv9pxT2DTBzsJis BBipaj6Lk6Ut100V0l28snqpb8AQs12Hbz/GufcLmyLUOrRnKmOE04KqERrJd7oSClrc IUjivGS/7QI3tbixLPBV9d6Jcgahre0sxl/y6uukpuSQmdYKD5wn255Bh2lmeHZ/26xQ OOTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=SO+2PJFvy8zvvZotKoGxEsNVGgDUITqV+Ms/8dao8Hw=; fh=lQz/rKU3LXHHcxNc9pIU98FUjceNg5wKxnoFSto6I+0=; b=XBlcwADxe3KxF5O4aLkH20j4CjV3KyjHicTdU/cVHh+aWVVvY6Us7RT0DhSYb3So/m Y3JRB9h4HG3O04Qzkq6UiTx0Qlfga+K/Kj9bXpaM+6CSOzGZNL367R4JW4Lh93WBZ5nb cgLxVCTsyGxubrKJg/BAKLBM8Q5ucXCtlII484aGN6fGYVLOsm5vdZA5hNAORi9l1cBH ROH5l2ffkxgwT+ll6eRueZ8C6E1zSWTYOqO0t3zyu0RsZOghrzOoJ1UVCsZjU69dPsPB 3nzqMD2+DbrXG04Jp3WI60acNFXeizYt6oX/0VpGGLRMPshPyxr+RZK4q3Tz9UOIBykT jiXg==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1778174950; x=1778779750; 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=SO+2PJFvy8zvvZotKoGxEsNVGgDUITqV+Ms/8dao8Hw=; b=PhUWo8czB2lHH+LGE4He7m44xgFQCaO04otfDS8CrdUQ/4Xqe6rHvAxmdQLK3EWXrV wkSkwCuMHIdVgC8dwdt8iWUVrk5xJl8HhTNOGam6uo1x22yEztSrCO0I5c3pXMVOGQzs k37ARWveSdKlvmXPvU9YCqvlV8rwqmhfj3u8c4oCq15uTeyMbs+2LEMqI+7pb3417X/P T1NhRtyJrQRfZof1RmPmrMtWDXfZvzNmadxHwk+6eqZYqdhR2iXeehf9b3ZMJQYf1jSJ /qGmpfx/d1ZnIkkAVdjTG3H+jysiM+/XXdGIPappQ2G6vhumYakLvjdfyBaLkjPTYXDe JtaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778174950; x=1778779750; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=SO+2PJFvy8zvvZotKoGxEsNVGgDUITqV+Ms/8dao8Hw=; b=nI2SI0xk3hsKrfUrZCDQJM5ogQ/UIwxRY8cGtP+uIDg54Kp7zvQaP/ncPPZ2Uwq0d8 cNfedHhURnedXIpaOvSYx4VRLSCFty0ORSX3Sm4DXJiQCAZW8PQ+q3Ji8+rgpg5b23YQ sas587Mzg19T75U+jADsSlX+rrCovTjQ6LBlw1SOi1bWwSa+a0qVxkxb2ryiSsucz9lS uewOMLUaonrm306DjgLRhiuDToc5nB+UOT7VvIVpDqNP7QpePbT/ck28s1qi1u3WTSGb 0WLfmd5p8Pihd8glSaOX/HQEx37+7/cpwD9Jwobo1tL6t2OeSkdJNeJvYIYr2+3tMyx3 Oi8A== X-Forwarded-Encrypted: i=1; AFNElJ/Orc3aP38hcJMBprFiljoJPLV9bmz7FQ+3OAvfZ9hz3K3BoGgVXq0DFbqtqjrjBpqarl6M8PcS5xZsCQ==@lists.postgresql.org X-Gm-Message-State: AOJu0Yze7kzvPusl/iJAKTZzNSfbezWttIR3IEsaH6WVomNKk3jUz5qP arGujQN/OLot3PUjdNDKavwNZoOI8sk2CgSRwG9vIxUGFOik3kknQvS2GjfB/pUXL9eNmLqkvY9 lLG9icDnTsYTITGafQayW39SuyyATfQ+XUg== X-Gm-Gg: AeBDievF/sQBneZ75B2gc6zH032/v2T/2LxYeh7VKQId1YMDEgvgAlBiMDn93W0lEpZ lROO0GNFu3Du+xV2wKp8IS8KTlurVx92ojQFFFQkcXMG8ATbO1RpxMWDOWp1Kz8z2b0qHOM1t1c Bsji0ceNDC/QF8KWkZUOFGhvlks6kCYvGQOXwNtjcWoxi1m7q+rFUwLQ6sl1RzKQwahB6OIJK9h QxiD7sWQQCLGe4hsWW+yT7dGgA0u6O35rDksOtC5ta8kiiuY+YzWt8yKXtJSDIdZ1y3pOAFqXlz k1x+xlx3/ljM4fht28Vrm7WD X-Received: by 2002:a2e:9b06:0:b0:393:7a01:397d with SMTP id 38308e7fff4ca-393c421415bmr27255251fa.26.1778174950055; Thu, 07 May 2026 10:29:10 -0700 (PDT) MIME-Version: 1.0 References: <644bd38b51ca44fba9ee516ea71c7983@alte-leipziger.de> In-Reply-To: From: Raj Date: Thu, 7 May 2026 22:58:54 +0530 X-Gm-Features: AVHnY4ILsf8nXPO40ODJvxqQ1nhisxM88YZHi8snDgqfnbAoIV9zrj6EUaevuQE Message-ID: Subject: Re: Load test To: "kurt thepw.com" Cc: "Subramanian,Ramachandran" , Shubhang Joshi , Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000003f23fe06513d9e87" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003f23fe06513d9e87 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks On Thu, 7 May 2026, 20:38 kurt thepw.com, wrote: > The pgBadger log analysis tool may provide useful information: > > https://www.postgresql.org/about/news/pgbadger-v124-released-2772/ > ------------------------------ > *From:* Subramanian,Ramachandran < > ramachandran.subramanian@alte-leipziger.de> > *Sent:* Thursday, May 7, 2026 4:12 AM > *To:* Raj ; Shubhang Joshi < > shubhangjoshi2405@gmail.com> > *Cc:* Pgsql-admin > *Subject:* AW: Load test > > > I am a newbie, just sharing what I have learnt so far. > > > > > > Try creating queries on pg_stat_activity and run them periodically during > the load test to get the metrics. ( Maybe append to a CSV file that you c= an > import into excel and analyze later ) . > > > > > > If you store sufficient pg_stat_statement ( based on your > pg_stat_statement.max value in your conf file ) , you may be able analyze > more details after the load test is done. > > > > Clean up your pg_stat_statement > > select pg_stat_statements_reset(); > > > > > > Set the parm to a higher value than the number of SQLs you expect to run > during the load test. Restart your instance. > > > > > > Let the load test finish. > > > > > > Look into your pg_stat_statements for all kinds of beautiful metrics. > > > > > > Clean up your pg_stat_statements if not needed anymore, reset your max > value and restart the instance. > > > > > > > > > > > > > > > > > > > > You can build on some basic queries like this > > > > > > > > SELECT pid, > > backend_type > > FROM pg_stat_activity > > ORDER BY pid, backend_type ; > > > > > > SELECT pid, > > usename, > > datname, > > client_addr, > > application_name, > > state, > > wait_event_type, > > wait_event, > > backend_start, > > query_start, > > now() - query_start AS runtime, > > query > > FROM pg_stat_activity > > WHERE state =3D 'active' > > ORDER BY runtime DESC; > > > > > > SELECT pid, > > now() - query_start AS duration, > > usename, > > query > > FROM pg_stat_activity > > WHERE state =3D 'active' > > AND now() - query_start > interval '10 seconds' > > ORDER BY duration DESC; > > ~ > > > > > > > > > > > > Freundliche Gr=C3=BC=C3=9Fe > > *i. A. Ramachandran Subramanian* > > Zentralbereich Informationstechnologie > > Alte Leipziger Lebensversicherung a. G. > > Hallesche Krankenversicherung a. G. > > ______________________ > > ALH Gruppe > Alte Leipziger-Platz 1, 61440 Oberursel > > Tel: +49 (6171) 66-4882 > Fax: +49 (6171) 66-800-4882 > E-Mail: ramachandran.subramanian@alte-leipziger.de > www.alte-leipziger.de > www.hallesche.de > > Alte Leipziger Lebensversicherung a. G., Alte Leipziger-Platz 1, 61440 > Oberursel > > > Vors. des Aufsichtsrats: Dr. Walter Botermann =C2=B7 Vorstand: Christoph = Bohn > (Vors.), Dr. J=C3=BCrgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Joch= en > Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek > > Sitz Oberursel (Taunus) =C2=B7 Rechtsform VVaG =C2=B7 Amtsgericht Bad Hom= burg v. d. > H. HRB 1583 =C2=B7 USt.-IdNr. DE 114106814 > > Hallesche Krankenversicherung a. G., L=C3=B6ffelstra=C3=9Fe 34-38, 70597 = Stuttgart > > > Vors. des Aufsichtsrats: Dr. Walter Botermann =C2=B7 Vorstand: Christoph = Bohn > (Vors.), Dr. J=C3=BCrgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Joch= en > Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek > > Sitz Stuttgart =C2=B7 Rechtsform VVaG =C2=B7 Amtsgericht Stuttgart HRB 26= 86 =C2=B7 > USt.-IdNr. DE 147802285 > > Beitr=C3=A4ge zu privaten Kranken- und Pflegekrankenversicherungen unterl= iegen > nicht der Versicherungsteuer (=C2=A7 4 (1) Nr. 5 b VersStG) =C2=B7 > Versicherungsleistungen sowie Ums=C3=A4tze aus > Versicherungsvertreter-/Maklert=C3=A4tigkeiten sind umsatzsteuerfrei > > Pflichtangaben der ALH Gruppe > gem=C3=A4=C3=9F =C2=A7 35a GmbHG bzw. =C2=A7 80 AktG > > *Von:* Raj > *Gesendet:* Donnerstag, 7. Mai 2026 09:07 > *An:* Shubhang Joshi > *Cc:* Pgsql-admin > *Betreff:* Re: Load test > > > > How do we check latency and throughput? > > On Thu, 7 May 2026, 09:52 Shubhang Joshi, > wrote: > > Hi Raj, > > During the load test, we should monitor the following key metrics: > > - Query Performance: Latency and throughput. > - System Resources: CPU and memory utilization, disk I/O, and cache > efficiency. > - Database Activity: Active connections and locking/blocking behavior. > - Logs: Any errors or anomalies observed. > > Additionally, we will need to compare the baseline performance with the > load test results to identify potential bottlenecks and areas for > optimization. > > Best regards, > Shubhang Joshi > > > > > > On Wed, 6 May, 2026, 2:20=E2=80=AFpm Raj, w= rote: > > Hi team, > > > > What are things we (dba) need to monitor during load test by application > team? > > > > If how we monitor, is addon for me. > > > > Thanks. > > --0000000000003f23fe06513d9e87 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks

On Thu, 7 May 2026, 20:38 kur= t thepw.com, <kurt@thepw.com> wrote:
The pgBadger log analysis tool may provide useful information:

From: = Subramanian,Ramachandran <ramachandran.subramani= an@alte-leipziger.de>
Sent: Thursday, May 7, 2026 4:12 AM
To: Raj <rajeshkumar.dba09@gmail.com>; Shubhang J= oshi <shubhangjoshi2405@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: AW: Load test
=C2=A0

I a= m a newbie, just sharing what I have learnt so far.

=C2= =A0

=C2= =A0

Try= creating queries on pg_stat_activity and run them periodically during the = load test to get the metrics. ( Maybe append to a CSV file that you can imp= ort into excel and analyze later ) .

=C2= =A0

=C2= =A0

If = you store sufficient pg_stat_statement ( based on your pg_stat_statement.ma= x value in your conf file ) , you may be able analyze more details after th= e load test is done.

=C2= =A0

Cle= an up your pg_stat_statement

sel= ect pg_stat_statements_reset();

=C2= =A0

=C2= =A0

Set= the parm to a higher value than the number of SQLs you expect to run durin= g the load test.=C2=A0 Restart your instance.

=C2= =A0

=C2= =A0

Let= the load test finish.

=C2= =A0

=C2= =A0

Loo= k into your pg_stat_statements for all kinds of beautiful metrics.

=C2= =A0

=C2= =A0

Cle= an up your pg_stat_statements if not needed anymore, reset your max value a= nd restart the instance.

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

=C2= =A0

You= can build on some basic queries like this

=C2= =A0

=C2= =A0

=C2= =A0

SEL= ECT pid,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 backend_type

FRO= M=C2=A0=C2=A0 pg_stat_activity

ORD= ER BY pid, backend_type ;

=C2= =A0

=C2= =A0

SEL= ECT pid,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 usename,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 datname,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 client_addr,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 application_name,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 state,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 wait_event_type,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 wait_event,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 backend_start,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 query_start,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 now() - query_start AS runtime,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 query

FRO= M pg_stat_activity

WHE= RE state =3D 'active'

ORD= ER BY runtime DESC;

=C2= =A0

=C2= =A0

SEL= ECT pid,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 now() - query_start AS duration,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 usename,

=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 query

FRO= M pg_stat_activity

WHE= RE state =3D 'active'

=C2= =A0 AND now() - query_start > interval '10 seconds'

ORD= ER BY duration DESC;

~

=C2=A0

=C2=A0

=C2=A0

=C2=A0

=C2=A0


Freundliche Gr=C3=BC=C3=9Fe


i. A. Ramachandran Subramanian

Zentralbereich Informationstechnologi= e

Alte Leipziger Lebensversicherung a.= G.

Hallesche Krankenversicherung a. G.<= /span>

______________________

ALH Gruppe
Alte Leipziger-Platz 1, 61440 Ober= ursel
Tel: +49 (6171) 66-4882
Fax: +49 (6171) 66-800-4882
E-Mail: ramachandran.subramanian@alte-leipziger.de<= /a>
www.alte-leipziger.de
w= ww.hallesche.de

Alte Leipziger Lebensversicherung a. = G., Alte Leipziger-Platz 1, 61440 = Oberursel

Vors. des Aufsichtsrats: D= r. Walter Botermann =C2=B7 Vorstand: Christoph Bohn (Vors.), Dr. J=C3=BCrge= n Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander = Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek

Sitz Oberursel (Taunus) =C2=B7 Rechts= form VVaG =C2=B7 Amtsgericht Bad Homburg v. d. H. HRB 1583 =C2=B7 USt.-IdNr= . DE 114106814


Hallesche Krankenversicherung a. G., = L=C3=B6ffelstra=C3=9Fe 34-38= , 70597 Stuttgart

Vors. des Aufsichtsrats: Dr. Walter B= otermann =C2=B7 Vorstand: Christoph Bohn (Vors.), Dr. J=C3=BCrgen Bierbaum = (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Chri= stian Pape, Wiltrud Pekarek, Udo Wilcsek

Sitz Stuttgart =C2=B7 Rechtsform VVaG= =C2=B7 Amtsgericht Stuttgart HRB 2686 =C2=B7 USt.-IdNr. DE 147802285

Beitr=C3=A4ge zu privaten Kranken- un= d Pflegekrankenversicherungen unterliegen nicht der Versicherungsteuer (=C2= =A7 4 (1) Nr. 5 b VersStG) =C2=B7 Versicherungsleistungen sowie Ums=C3=A4tz= e aus Versicherungsvertreter-/Maklert=C3=A4tigkeiten sind umsatzsteuerfrei

Pflichtangaben der ALH Gruppe gem=C3= =A4=C3=9F =C2=A7 35a GmbHG bzw. =C2=A7 80 AktG

Von: Raj <rajeshkumar.dba09@gmail.com>= ;
Gesendet: Donnerstag, 7. Mai 2026 09:07
An: Shubhang Joshi <shubhangjoshi2405@gmail.com><= br> Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Betreff: Re: Load test

=C2=A0

How do we check latency and throughput?

Hi Raj,

During the load test, we should monitor the following key metrics:

=C2=A0 - Query Performance: Latency and throughput.
=C2=A0 - System Resources: CPU and memory utilization, disk I/O, and cache = efficiency.
=C2=A0 - Database Activity: Active connections and locking/blocking behavio= r.
=C2=A0 - Logs: Any errors or anomalies observed.

Additionally, we will need to compare the baseline performance with the loa= d test results to identify potential bottlenecks and areas for optimization= .

Best regards,
Shubhang Joshi

=C2=A0

=C2=A0

On Wed, 6 May, 2026, 2:20=E2=80=AFpm Raj, <rajeshkumar.dba09= @gmail.com> wrote:

Hi team,

=C2=A0

What are things we (dba) need to monitor during load test by application= team?=C2=A0

=C2=A0

If how we monitor, is addon for me.

=C2=A0

Thanks.

--0000000000003f23fe06513d9e87--