Re: Allow non-superuser to cancel superuser tasks.

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Michael Paquier <michael(at)paquier(dot)xyz>, "Leung, Anthony" <antholeu(at)amazon(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow non-superuser to cancel superuser tasks.
Date: 2024-11-26 17:11:02
Message-ID: CALdSSPj8PxOsU2YcDZdZmcZe-oC=FJRrAEZDuirMQd4eYCPU7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 23 Nov 2024, 07:44 Nathan Bossart, <nathandbossart(at)gmail(dot)com> wrote:

> On Fri, Nov 22, 2024 at 06:13:16PM -0500, Andres Freund wrote:
> >> - if (procStatus && procStatus->st_backendType ==
> B_AUTOVAC_WORKER)
> >> + if (pgstat_get_backend_type(pid) == B_AUTOVAC_WORKER)
> >
> > Because we already mapped the pid to a ProcNumber, it'd be cheaper to
> access
> > the backend status via procnumber.
>
> D'oh, I missed that ProcNumber could be used as an index for the
> BackendStatusArray. Is the attached more like what you are imagining?
>
> > We don't need the pgstat_begin_read_activity() protocol when just
> accessing a
> > single 4 byte value - we assume in lots of places that can be read in a
> > non-tearable way.
> >
> >> + if
> (pgstat_read_activity_complete(before_changecount,
> >> +
> after_changecount))
> >> + break;
> >> +
> >> + CHECK_FOR_INTERRUPTS();
> >> + }
> >> +
> >> + if (found)
> >> + return beentry->st_backendType;
> >
> > But if we were to follow it, we'd certainly need to use it here too.
>
> I see.
>
> --
> nathan
>
Hi!
LGTM

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-11-26 17:13:55 Re: Self contradictory examining on rel's baserestrictinfo
Previous Message Bruce Momjian 2024-11-26 17:08:54 Re: Doc: typo in config.sgml