From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
---|---|
To: | MELIANI Fayçal <accmeliani(at)gmail(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Disable PGadmin tools (backup / restore ) |
Date: | 2024-07-09 04:58:52 |
Message-ID: | CAM9w-_ktqhL1bU=ktEfoTbBEhBuwg+UBW19+e3yUsMw1Zm-7aw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi MELIANI,
Currently, you cannot do that. What you can do is remove the binary paths
location from preferences so that backup won't start.
On Mon, Jul 8, 2024 at 7:14 PM MELIANI Fayçal <accmeliani(at)gmail(dot)com> wrote:
> Hello,
>
> We are using pgAdmin in a Kubernetes environment and are looking to
> restrict users from performing backup or restore operations from the
> pgAdmin console. Performing a backup operation, for instance, from within
> the pod could potentially crash the pod in case of an OOMKill or saturate
> the PVC, thereby causing pgAdmin to stop.
>
> We would like to inquire if there is a way to customize the pgAdmin Docker
> image to enforce restrictions on these specific operations from the
> console. Could you provide guidance or recommendations on how to configure
> pgAdmin to meet these requirements ?
>
> Thank you in advance for your assistance and advice.
>
> Best regards,
>
--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*
<https://www.enterprisedb.com/>
"Don't Complain about Heat, Plant a TREE"
From | Date | Subject | |
---|---|---|---|
Next Message | Yogesh Mahajan | 2024-07-09 05:41:27 | Re: Issue with Viewing Created Table in pgAdmin |
Previous Message | MELIANI Fayçal | 2024-07-08 13:44:25 | Disable PGadmin tools (backup / restore ) |