From: | Kashif Zeeshan <kashi(dot)zeeshan(at)gmail(dot)com> |
---|---|
To: | RAJAMOHAN <garajamohan(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Prevent users from executing pg_dump against tables |
Date: | 2024-05-02 06:11:55 |
Message-ID: | CAAPsdhcYUEnhx51Mq9DKkXve=Twg=n8cKMa95Lfjzy4H8_+jdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi RAJAMOHAN
There is not a direct way to restrict a table not to be allowed to be
backed up by pg_dump.
But you can use the RLS (ROW LEVEL SECURITY) policy to restrict access.
Regards
Kashif Zeeshan
Bitnine Global
On Thu, May 2, 2024 at 10:47 AM RAJAMOHAN <garajamohan(at)gmail(dot)com> wrote:
> Hello all,
>
> In our production db infrastructure, we have one read_only role which has
> read privileges against all tables in schema A.
>
> We are planning to grant this role to some developers for viewing the
> data, but also I want to limit the users from executing statements like
> copy or using pg_dump. Main reason being I don't want the data to be copied
> from the database to their local machines.
>
> I tried by implementing triggers, but was not able to figure out a way to
> restrict the pg_dump and allow only select statements.
>
> Postgresql version - 12
> Ec2 based postgres database
>
> Is there a way to implement this? Please advise.
>
>
> Thanks & Regards,
> Rajamohan.J
> Devops Cloud Architect
> Email:garajamohan(at)gmail(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Fire Emerald | 2024-05-02 09:20:48 | Re: How to interpret 'depends on' errors in pg_restore? |
Previous Message | RAJAMOHAN | 2024-05-02 05:46:42 | Prevent users from executing pg_dump against tables |