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

Поиск
Список
Период
Сортировка
От Jacob Champion
Тема Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible
Дата
Msg-id CAOYmi+=tkATXFmvvAzwLTwq52YrezFopeoPrkW3pXv6LDFYT6A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible  (Jacob Champion <jacob.champion@enterprisedb.com>)
Ответы Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible
Список pgsql-hackers
On Tue, Mar 4, 2025 at 4:26 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> But attaching to that injection point succeeded above, for us to have
> gotten to this point... Does that error message indicate that the
> point itself doesn't exist, or that nothing is currently waiting?

Looks like the latter. With the following diff I can reproduce locally:

    --- a/src/backend/utils/init/postinit.c
    +++ b/src/backend/utils/init/postinit.c
    @@ -730,6 +730,7 @@ InitPostgres(const char *in_dbname, Oid dboid,
            if (!bootstrap)
            {
                    pgstat_bestart_initial();
    +               pg_usleep(1000000);
                    INJECTION_POINT("init-pre-auth");
            }

So I've misunderstood the API. I should have added a background
version of $node->wait_for_event(), or similar.

I'll work on a fix, but it probably won't be fast since I need to
learn more about the injection points architecture. The test may need
to be disabled, or the patch backed out, depending on how painful the
flake is for everybody.

Thanks, and sorry,
--Jacob



В списке pgsql-hackers по дате отправления: