Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal and therefore subject to change. This information is provided without warranty of any kind

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion created with the classic syntax use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For

the file in user $HOME. The email subject line includes the utility name, timestamp, status, and the name of the Greenplum Database master. This is an example subject line for a gpbackup email. Note: be a key and certificate pair for the master host and a pair for the standby master host with a subject CN (Common Name) for the master host and standby master host. A self-signed certificate can be Greenplum Database system, the user's Kerberos principle name will be the Greenplum Database role name, subject to transformations specified in the options field of the gss entry in the Greenplum Database pg_hba

the file in user $HOME. The email subject line includes the utility name, timestamp, status, and the name of the Greenplum Database master. This is an example subject line for a gpbackup email. Note: be a key and certificate pair for the master host and a pair for the standby master host with a subject CN (Common Name) for the master host and standby master host. A self-signed certificate can be Greenplum Database system, the user's Kerberos principle name will be the Greenplum Database role name, subject to transformations specified in the options field of the gss entry in the Greenplum Database pg_hba

the file in user $HOME. The email subject line includes the utility name, timestamp, status, and the name of the Greenplum Database master. This is an example subject line for a gpbackup email. gpbackup be a key and certificate pair for the master host and a pair for the standby master host with a subject CN (Common Name) for the master host and standby master host. A self-signed certificate can be used Greenplum Database system, the user's Kerberos principle name will be the Greenplum Database role name, subject to transformations specified in the options field of the gss entry in the Greenplum Database pg_hba

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion Partition Partitioned tables use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion Partition Partitioned tables use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion Partition Partitioned tables use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion Partition Partitioned tables use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For

set, only users of that realm will be accepted. If it is not set, users of any realm can connect, subject to whatever user name mapping is done. LDAP Authentication You can authenticate against an LDAP Greenplum Database records the username for all auditable events, when the event is initiated by a subject outside the Greenplum Database. Greenplum Database prevents unauthorized modification and deletion Partition Partitioned tables use the following naming convention. Partitioned subtable names are subject to uniqueness requirements and length limitations. __prt_ For