performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords

performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords table shows the supported encryption algorithms. Value Functionality Built-in With OpenSSL MD5 yes yes SHA1 yes yes SHA224/256/384/512 yes yes 1 Other digest algorithms no yes 2 Blowfish yes yes AES

performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords

performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords

performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the allows PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. VMware Greenplum 6 Documentation VMware, Inc. 508 Because pgcrypto functions

performance improvements as you only need to return the columns of interest to you. All compression algorithms can be used with either row or column-oriented tables, but Run-Length Encoded (RLE) compression will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords

will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords encryption algorithms. Table 1. Pgcrypto Supported Encryption Functions Value Functionality Built-in With OpenSSL MD5 yes yes SHA1 yes yes SHA224/256/384/512 yes yes 1. Other digest algorithms no yes

will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords encryption algorithms. Table 1. Pgcrypto Supported Encryption Functions Value Functionality Built-in With OpenSSL MD5 yes yes SHA1 yes yes SHA224/256/384/512 yes yes 1. Other digest algorithms no yes

will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords encryption algorithms. Table 1. Pgcrypto Supported Encryption Functions Value Functionality Built-in With OpenSSL MD5 yes yes SHA1 yes yes SHA224/256/384/512 yes yes 1. Other digest algorithms no yes

will use legacy hash operators when loading the data. This is because Greenplum 6 has new hash algorithms that map distribution keys to segments, but the data in the backup set must be restored to the PGP encryption functions to compress data before encrypting. When compiled with OpenSSL, more algorithms will be available. Because pgcrypto functions run inside the database server, the data and passwords shows the supported encryption algorithms. Value Functionality Built-in With OpenSSL MD5 yes yes SHA1 yes yes SHA224/256/384/512 yes yes 1. Other digest algorithms no yes 2 Blowfish yes yes AES