MIME-Version: 1.0
References: <Z8fW2PcLkkXaK9L8@paquier.xyz>
 <CAOYmi+=+py0pJSKCvZSXZbA9CRxc=OtLXx90BRDj-Rdx2f2WDg@mail.gmail.com>
 <CAOYmi+nxNCQcTQE-tQ7Lwpe4cYc1u-yxwEe5kt2AVN+DXXVVbQ@mail.gmail.com>
 <tfc4r4sr5m47f42nwsymadafjr3h7sjskilq62s64ujdpi4oxc@dfgxzqcxjrjy>
 <CAOYmi+n0EU-O5fRR9SmtekLp4XZt80OieMYJapfy=Z9zTkG6rQ@mail.gmail.com>
 <lfzorjb3rnywykl4dazkk24h3dlqulufwmvknj3hby2tc6hwh2@vprzh3stdr6h>
 <Z8kfmvKOfYA91sNE@paquier.xyz>
 <CAOYmi+nbgAifBRHy6_dSFGcwtRk78YTbVTO=tb+1HwqM0gwbCw@mail.gmail.com>
 <Z8osml5sp7Q3LIhZ@paquier.xyz>
 <CAOYmi+kHY8HZ5RdXGT1bVZzkAq7ta=--YSGehLr35HRjF4Fyug@mail.gmail.com>
 <qvqojlk7efqr47xluqsvvuxvc6vbxjkn3jaqvcgnctmimvs2us@t3a7xrvblm2r>
In-Reply-To: <qvqojlk7efqr47xluqsvvuxvc6vbxjkn3jaqvcgnctmimvs2us@t3a7xrvblm2r>
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Fri, 7 Mar 2025 09:03:18 -0800
Message-ID: 
 <CAOYmi+=fVn7GJNEvtMBDZD_25S40iFD3r7PLOS6gOwJMAdEwMQ@mail.gmail.com>
Subject: Re: [PATCH] pg_stat_activity: make slow/hanging authentication more
 visible
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>,
 Robert Haas <robertmhaas@gmail.com>,
	Noah Misch <noah@leadboat.com>, Andrew Dunstan <andrew@dunslane.net>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Euler Taveira <euler.taveira@enterprisedb.com>,
 Daniel Gustafsson <daniel@yesql.se>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAOYmi%2B%3DfVn7GJNEvtMBDZD_25S40iFD3r7PLOS6gOwJMAdEwMQ%40mail.gmail.com>
Precedence: bulk

On Fri, Mar 7, 2025 at 8:38=E2=80=AFAM Andres Freund <andres@anarazel.de> w=
rote:
> FWIW, I continue to think that this is a misuse of wait events. We should=
n't
> use them as a poor man's general purpose tracing framework.

Well, okay. That's frustrating.

If I return to the original design, but replace all of the high-level
wait events with calls to pgstat_report_activity(), does that work?

--Jacob