MIME-Version: 1.0
In-Reply-To: <CAFzdntvuzVvyj48V-bmo09ui8THtkMY-h5xaFqBOh5e_16nc3g@mail.gmail.com>
References: <CAFzdntvuzVvyj48V-bmo09ui8THtkMY-h5xaFqBOh5e_16nc3g@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Thu, 2 May 2024 05:24:18 -0700
Message-ID: <CAKFQuwa2gb6QKvUVuGTy4T1cScKgJEhaxvqwKDeJAZgpxpTWYg@mail.gmail.com>
Subject: Re: Prevent users from executing pg_dump against tables
To: RAJAMOHAN <garajamohan@gmail.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000acbac4061777aeeb"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwa2gb6QKvUVuGTy4T1cScKgJEhaxvqwKDeJAZgpxpTWYg%40mail.gmail.com>
Precedence: bulk

--000000000000acbac4061777aeeb
Content-Type: text/plain; charset="UTF-8"

On Wednesday, May 1, 2024, RAJAMOHAN <garajamohan@gmail.com> wrote:

>
>  Main reason being I don't want the data to be copied from the database to
> their local machines.
>

You cannot stop it being copied to their local machine, you can only make
it difficult.  And really not that difficult.

Trust but verify - i.e., use something like pg_audit.

David J.

--000000000000acbac4061777aeeb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, May 1, 2024, RAJAMOHAN &lt;<a href=3D"mailto:garajamohan@gmai=
l.com">garajamohan@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div><br></div><div>=C2=A0Main reason being I don&#39;t=
 want the data to be copied from the database to their local machines.</div=
></div></blockquote><div><br></div><div>You cannot stop it being copied to =
their local machine, you can only make it difficult.=C2=A0 And really not t=
hat difficult.</div><div><br></div><div>Trust but verify - i.e., use someth=
ing like pg_audit.</div><div>=C2=A0</div><div>David J.</div><div><br></div>

--000000000000acbac4061777aeeb--