In order to deal with PostgreSQL binding views and non-obvious cascade object dropping via standart "table" materialization, I propose using custom materialization strategy "truncate+insert", cause TRUNCATE operation in Greenplum is transactional and can be rolled back.
In order to deal with PostgreSQL binding views and non-obvious cascade object dropping via standart "table" materialization, I propose using custom materialization strategy "truncate+insert", cause TRUNCATE operation in Greenplum is transactional and can be rolled back.