ALTER DEFAULT PRIVILEGES FOR ROLE - Mailing list pgsql-general

From Hilbert, Karin
Subject ALTER DEFAULT PRIVILEGES FOR ROLE
Date
Msg-id DM6PR02MB48761279ADE0CD89EF417E4189900@DM6PR02MB4876.namprd02.prod.outlook.com
Whole thread Raw
Responses Re: ALTER DEFAULT PRIVILEGES FOR ROLE  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general

After a database was updated by the application, a schema dump showed the following default privilege statements:

--
-- Name: DEFAULT PRIVILEGES FOR SEQUENCES; Type: DEFAULT ACL; Schema: public; Owner: gitlab_dbo
--

ALTER DEFAULT PRIVILEGES FOR ROLE <dbowner> IN SCHEMA public REVOKE ALL ON SEQUENCES  FROM <dbowner>;
ALTER DEFAULT PRIVILEGES FOR ROLE <dbowner> IN SCHEMA public GRANT SELECT,USAGE ON SEQUENCES  TO <appuser>;


--
-- Name: DEFAULT PRIVILEGES FOR TABLES; Type: DEFAULT ACL; Schema: public; Owner: <dbowner>
--

ALTER DEFAULT PRIVILEGES FOR ROLE <dbowner> IN SCHEMA public REVOKE ALL ON TABLES  FROM <dbowner>;
ALTER DEFAULT PRIVILEGES FOR ROLE <dbowner> IN SCHEMA public GRANT SELECT,INSERT,DELETE,UPDATE ON TABLES  TO <appuser>;

Why would you want to revoke all privileges from the dbowner?
It actually had granted the privileges to PUBLIC, but I revoked those privileges & changed it to the app account.


What is the difference between these statements?:
ALTER DEFAULT PRIVILEGES FOR ROLE <dbowner> IN SCHEMA public GRANT ...  TO <appuser>;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ... TO <appuser>;



Karin Hilbert
Database Specialist
Administrative Information Services
Pennsylvania State University
25 Shields Bldg., University Park, PA  16802
Work - 814-863-3633
Email - ioh1@psu.edu
IM - ioh1@chat.psu.edu

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Old tsearch functions
Next
From: Adrian Klaver
Date:
Subject: Re: ALTER DEFAULT PRIVILEGES FOR ROLE