From: | MELIANI Fayçal <accmeliani(at)gmail(dot)com> |
---|---|
To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Disable PGadmin tools (backup / restore ) |
Date: | 2024-07-09 13:27:05 |
Message-ID: | CAPqAYu0r2xGBEN6aVpa9J7KSR-KcybHjephjKA2jdMs_sWRAAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Aditya,
It works well, thank you very much for your support and quick response.
Best regards.
Le mar. 9 juil. 2024 à 06:59, Aditya Toshniwal <
aditya(dot)toshniwal(at)enterprisedb(dot)com> a écrit :
> 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-10 05:06:46 | Re: Issue with Viewing Created Table in pgAdmin |
Previous Message | Yogesh Mahajan | 2024-07-09 09:58:26 | Re: Issue with Viewing Created Table in pgAdmin |