Re: BUG #18667: Default Permission Role Group

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "seyda-aydin(at)hotmail(dot)com" <seyda-aydin(at)hotmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18667: Default Permission Role Group
Date: 2024-10-21 12:53:54
Message-ID: CAKFQuwYG0Wd2U3ypbZovk78+KMVRr5bwAhj8dBVdEdNLQCFi5Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Monday, October 21, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18667
> Logged by: seyda aydin
> Email address: seyda-aydin(at)hotmail(dot)com
> PostgreSQL version: 15.0
> Operating system: previgles
> Description:
>
> Hello,
>
> We use Postgresql -15. We need a account and the account should read all
> data. We previgles this group permission . (read_all_data)
>
> When I add this group privigles, the account have pg_dump permission. Why?
> How do I prevent this?.
>

There is no pg_dump permission. But an account that can read all data is
certainly capable of exercising that right via the pg_dump utility, or any
other client for that matter.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-10-21 14:20:12 Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
Previous Message Tender Wang 2024-10-21 12:52:34 Re: BUG #18664: Assert in BeginCopyTo() fails when source DML query rewritten with notifying rule