From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: chandan Kumar <chandan.issyoga@gmail.com>,
        pgsql-general@lists.postgresql.org
Subject: Re: Fwd: SQL transactions executing from VMSS
In-reply-to: <74357b166a8e522d1a14aca7d763d0f0365df5da.camel@cybertec.at>
References: <CAHV6zVksAQQDiHXmDB-DHCc2Sk0fJjY_ByC4O-HQjOhUa3fOwg@mail.gmail.com> <CAHV6zVn=8LrKPaHL4Qceq6+_jkwJzFpvvrRpVKseditBhtHrFw@mail.gmail.com> <74357b166a8e522d1a14aca7d763d0f0365df5da.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Mon, 28 Apr 2025 11:05:31 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <698409.1745838121.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Apr 2025 07:02:01 -0400
Message-ID: <698410.1745838121@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/698410.1745838121%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> I think that the answer you didn't get was as helpful as your problem de=
scription:
>   "I got some statement that is slow, but I will neither tell you the st=
atement nor
>    show you the execution plan.  What is the cause of the slowness?"

The OP did say that the execution plan was the same on both servers.
That would appear to imply that the problem is in the client-side
software stack.  Unfortunately, this is not the place to come for
expertise in VMSS (I for one have no idea what that even is).
Suggest asking in whatever community exists around that software.

			regards, tom lane