The geodatabase administrator in PostgreSQL is a database login role named sde.
This account is responsible for administration of the following:
- The geodatabase system tables, triggers, functions, procedures, and SQL types
- Geodatabase versions
Because the geodatabase administrator owns all the geodatabase system files, directories, and tables, this account must be created before the geodatabase can be created. If you use the Create Enterprise Geodatabase geoprocessing tool or script to create a geodatabase in PostgreSQL, the tool creates the sde user and its schema for you and grants the privileges necessary to create a geodatabase. If you use the Enable Enterprise Geodatabase geoprocessing tool, script, or wizard to enable geodatabase functionality in an existing PostgreSQL database, the database administrator must create the sde user and schema and grant the privileges required to create a geodatabase.
Keep in mind that the geodatabase administrator is not the same as the database administrator. Although conditions at your site may necessitate that the geodatabase administrator have superuser status in the database cluster, this is not required for day-to-day operation of a geodatabase in PostgreSQL.
The sde login role and schema
In PostgreSQL, login roles do not automatically have a schema with the same name as their user name. However, to use PostgreSQL with ArcGIS, your user names must have corresponding default schema names. This applies to the sde user as well as nonadministrative users that own data.
Esri recommends that the sde schema only be used to store the geodatabase repository. You should create separate users and schemas to store datasets such as feature classes or tables. Following the practice of storing only geodatabase system objects in the sde user's schema simplifies the management of the geodatabase and makes it easier for you to delete the geodatabase from your database if you ever decide to do so.