Re: New default role- 'pg_read_all_data' - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: New default role- 'pg_read_all_data'
Date
Msg-id 20200828123847.GV29590@tamriel.snowman.net
Whole thread Raw
In response to Re: New default role- 'pg_read_all_data'  (Magnus Hagander <magnus@hagander.net>)
Responses Re: New default role- 'pg_read_all_data'  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Greetings,

* Magnus Hagander (magnus@hagander.net) wrote:
> Without having actually looked at the code, definite +1 for this feature.
> It's much requested...

Thanks.

> But, should we also have a pg_write_all_data to go along with it?

Perhaps, but could certainly be a different patch, and it'd need to be
better defined, it seems to me...  read_all is pretty straight-forward
(the general goal being "make pg_dumpall/pg_dump work"), what would
write mean?  INSERT?  DELETE?  TRUNCATE?  ALTER TABLE?  System catalogs?

Doesn't seem like you could just declare it to be 'allow pg_restore'
either, as that might include creating untrusted functions, et al.

Thanks,

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: SyncRepLock acquired exclusively in default configuration
Next
From: Stephen Frost
Date:
Subject: Re: New default role- 'pg_read_all_data'