| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Subject: | Re: Misplaced superuser check in pg_log_backend_memory_contexts() |
| Date: | 2021-06-06 15:13:40 |
| Message-ID: | 635185.1622992420@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Sun, Jun 06, 2021 at 03:53:10PM +0900, Michael Paquier wrote:
>> It seems to me that we had better check for a superuser at the
>> beginning of the function, like in the attached.
> However +1 for the patch, as it seems more consistent to always get a
> permission failure if you're not a superuser.
Yeah, it's just weird if such a check is not the first thing
in the function. Even if you can convince yourself that the
actions taken before that don't create any security issue today,
it's not hard to imagine that innocent future code rearrangements
could break that argument. What's the value of postponing the
check anyway?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Omar Kilani | 2021-06-06 15:18:51 | Re: Strangeness with UNIQUE indexes and UTF-8 |
| Previous Message | Omar Kilani | 2021-06-06 15:08:51 | Re: Strangeness with UNIQUE indexes and UTF-8 |