Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible

From: Noah Misch <noah(at)leadboat(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Euler Taveira <euler(dot)taveira(at)enterprisedb(dot)com>
Subject: Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible
Date: 2024-07-09 00:04:01
Message-ID: 20240709000401.0b.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 08, 2024 at 02:09:21PM -0700, Jacob Champion wrote:
> On Sun, Jun 30, 2024 at 10:48 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > That said, it
> > may be more fruitful to arrange for authentication timeout to cut through PAM
> > etc.
>
> That seems mostly out of our hands -- the misbehaving modules are free
> to ignore our signals (and do). Is there another way to force the
> issue?

Two ways at least (neither of them cheap):
- Invoke PAM in a subprocess, and SIGKILL that process if needed.
- Modify the module to be interruptible.

> > Hanging connection slots hurt even if they lack an xmin.
>
> Oh, would releasing the xmin not really move the needle, then?

It still moves the needle.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2024-07-09 00:05:07 Re: Why do we define HAVE_GSSAPI_EXT_H?
Previous Message Michael Paquier 2024-07-08 23:52:25 Re: pgsql: Add pg_get_acl() to get the ACL for a database object