Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

BLOB storage in Postgres databases

Updated on November 29, 2016

To improve performance of Postgres databases, BLOB columns in new tables that are created during installation, upgrade, or DDL (Data Definition Language) and schema generation are altered to use external storage instead of expanded storage. Existing tables with BLOB columns are not altered during an upgrade. System management utilities that create tables with BLOB columns, such as import, still default to use expanded storage.

You can alter existing tables to use external storage when new data is inserted into them by using the following command:

alter table <schema name>.<table_name> alter column <column name> set storage external

Use the Postgres VACUUM command to rebuild the table and force existing BLOB columns to use external storage.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us