| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Nikolay Samokhvalov <nik(at)postgres(dot)ai>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kirk Wolak <wolakk(at)gmail(dot)com>, Andrey Borodin <amborodin(at)acm(dot)org>, aekorotkov(at)gmail(dot)com |
| Subject: | Re: Missing wait events (gap analysis) |
| Date: | 2025-11-24 17:18:34 |
| Message-ID: | 202511241712.3pnzf5mks3dr@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Nov-24, Matthias van de Meent wrote:
> On Sat, 22 Nov 2025 at 01:43, Nikolay Samokhvalov <nik(at)postgres(dot)ai> wrote:
> > Before moving forward with proposals of specific patches, I wanted
> > to hear opinions -- does it make sense to work in this direction?
>
> I don't think it's a bad idea to add wait events in potential wait
> points in code.
There are things that I think it makes sense to cover, such as DNS
lookups, calls to external libraries for authentication, and so on. I'm
not so sure that it is useful to distinguish things like one type of DNS
lookup from another. Low-level operations such as file unlinking also
sounds like a reasonable thing to report separately, as long as it
doesn't break reporting for something else ...
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Ninguna manada de bestias tiene una voz tan horrible como la humana" (Orual)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2025-11-24 17:26:58 | Re: Cygwin support |
| Previous Message | Álvaro Herrera | 2025-11-24 17:08:24 | Re: Extended test coverage and docs for SSL passphrase commands |