From 1217cb23897421754631dc033f0c0d324e40ddf2 Mon Sep 17 00:00:00 2001 From: Jason Etheridge Date: Tue, 14 Mar 2017 13:22:51 -0400 Subject: [PATCH] use UNLOGGED tables for the base staging tables Signed-off-by: Jason Etheridge --- sql/base/base.sql | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/sql/base/base.sql b/sql/base/base.sql index bd2b58a..8f16f68 100644 --- a/sql/base/base.sql +++ b/sql/base/base.sql @@ -244,7 +244,7 @@ CREATE OR REPLACE FUNCTION migration_tools.build_specific_base_staging_table (TE BEGIN base_staging_table = REPLACE( production_table, '.', '_' ); --RAISE INFO 'In migration_tools.build_specific_base_staging_table(%,%) -> %', migration_schema, production_table, base_staging_table; - PERFORM migration_tools.exec( $1, 'CREATE TABLE ' || migration_schema || '.' || base_staging_table || ' ( LIKE ' || production_table || ' INCLUDING DEFAULTS EXCLUDING CONSTRAINTS );' ); + PERFORM migration_tools.exec( $1, 'CREATE UNLOGGED TABLE ' || migration_schema || '.' || base_staging_table || ' ( LIKE ' || production_table || ' INCLUDING DEFAULTS EXCLUDING CONSTRAINTS );' ); PERFORM migration_tools.exec( $1, ' INSERT INTO ' || migration_schema || '.fields_requiring_mapping SELECT table_schema, table_name, column_name, data_type -- 1.7.2.5