| From: | Alexander Petrossian <alexander(dot)petrossian(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Luca Ferrari <fluca1978(at)gmail(dot)com>, Александр Петросян <paf(at)yandex(dot)ru>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: debugger from superuser only.... why? |
| Date: | 2023-09-27 11:30:43 |
| Message-ID: | 938407CE-46E9-4699-AB0C-DB02F2755B2A@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 25 сент. 2023 г., в 17:28, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> написал(а):
> Alexander Petrossian <alexander(dot)petrossian(at)gmail(dot)com> writes:
>>>> I am wondering why is this, why not allow debugging for non-privileged users?
> Even if there's a way to restrict
> debugging connections to sessions owned by the same user,
I guess, there is such a way. Looks trivial...
> you’d have a big problem with being able to change the behavior of
> security-definer functions.
Could you please elaborate on this, Tom?
My worry is that it is very inconvenient.
And if reasons are not super-solid, maybe one can budge the Author? :)
> Clearly, the authors of pldebugger
> decided that was a can of worms they didn't care to open.
Unless one wants to go fishing ;)
PAF
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-27 13:52:09 | Re: debugger from superuser only.... why? |
| Previous Message | Erik Wienhold | 2023-09-27 11:05:45 | Re: Regarding PostgreSQL 15.4 |