On Wed, Nov 26, 2025 at 4:45 AM Tom Lane wrote:
> immerrr again writes:
> > On Wed, Nov 26, 2025 at 1:08 AM Tom Lane wrote:
> >> The missing step here is
> >> DROP OWNED BY test_role;
>
> > It just makes me uneasy to run a command with such potential for
> I have written a couple of queries to manually clean up the system tables
pg_init_privs/pg_shdepends instead (see [1])
Sorry, wrong link [1]. Should have been
1.
https://www.postgresql.org/message-id/CAERznn-QWVpAvqnyF%3DrZfiuxkeDG0tym_rY%2BRuEkSPWvzgi67Q%40mail.gmail.com
>
Hi Tom,
On Wed, Nov 26, 2025 at 1:08 AM Tom Lane wrote:
> The missing step here is
>
> DROP OWNED BY test_role;
> ...
> See discussion here:
> ...
I had gone through that thread before posting, and yes, I mentioned "DROP
OWNED BY" in my original message. Is this what everyone is doing these
day
tements_info
> privileges for view pg_stat_statements
>
> Is there some difference in the configuration that I'm not accounting for?
>
> Thanks
>
>
> On Tue, Nov 25, 2025 at 11:49 PM Pavel Luzanov
> wrote:
>
>> Hi
>>
>> On 24.11.2025 18:59, imm
d
postgres:16.9
ae9fe66613867d4db6019bbc0806ef57b5bf7e8b83b10ee0dbb422c2d146d701
[nix-shell:~]$ psql postgres://postgres:pg_test_init_privs@localhost:
<
wrote:
> Hi
>
> On 24.11.2025 18:59, immerrr again wrote:
>
> First time trying to configure a PG cluster by the book, I
Hi everyone,
First time trying to configure a PG cluster by the book, I want to create a
role with read permissions on all current and future tables in the current
db. It looks smth like this
CREATE ROLE test_role;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO test_role;
ALTER DEFAULT PRIVILEGES
