| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | "Alexander Petrossian (PAF)" <alexander(dot)petrossian(at)gmail(dot)com> |
| Cc: | "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-22 15:00:34 |
| Message-ID: | CAKoxK+671=LvaNDpBaK34fks1+TdBttN13vfELSUi0eaTOoqkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 22, 2023 at 2:00 PM Alexander Petrossian (PAF)
<alexander(dot)petrossian(at)gmail(dot)com> wrote:
> Some mail list you would suggest, Luka?
>
pgadmin mailing list, or ask EDB somehwere.
>>
>> > SELECT * FROM pldbg_create_listener();
>> uh oh, it mentions a listener...then there must be some "sender"
>> somehwere, that probably needs privileges.
>
>
> Surprisingly this passes OK under non-privileged user.
I meant: somewhere else there must be something that connects back and
requires privileges.
Also, this (not tried) does not seem to require other privileges
<https://github.com/OmniDB/plpgsql_debugger>.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-09-22 15:18:34 | How to fork pg_dump or psql w/o leaking secrets? |
| Previous Message | Francisco Olarte | 2023-09-22 14:02:55 | Re: How to fork pg_dump or psql w/o leaking secrets? |