Contents x
    Data Destination - PostgreSQL
      • Print
      • PDF
      Contents

      Data Destination - PostgreSQL

        • Print
        • PDF
        Article summary

        summary

        Help Page for Data Settings for ETL Configuration to PostgreSQL.

        constraints

        • none in particular

        Setting items

        STEP1 Basic settings

        item nameindispensabledefault valueContents
        PostgreSQL Connection ConfigurationYes-Select the previously registered Connection Configuration that has the necessary permissions for this ETL Configuration.
        databaseYes-Specify the name of a database that exists on Data Destination PostgreSQL.
        schemaYespublicSpecify the name of the schema that exists in the Data Destination database.
        You can also load a list from the Load Schema List.
        tableYes-Specifies the name of the Data Destination table.
        If the entered table name does not exist, a new table will be created upon transfer.
        transfer modeYes-Select the transfer mode. See Transfer Mode for details.
        Default time zoneYesUTCSpecifies which time zone is used for columns of type timestamp.

        STEP2 Detailed settings

        item nameindispensabledefault valueDetails
        Maximum number of retriesYes12Specifies the maximum number of retries to be performed.
        Retry wait time (ms)Yes1000Specifies the waiting time for retries.
        Maximum retry wait time (ms)Yes1800000Specifies the maximum time to wait for retries.
        SQL to execute before loadingNo-Describes the query to be executed before transfer.
        SQL to execute after loadingNo-Describes the query to be executed after the transfer.

        transfer mode

        mode (musical mode, mode of probability distribution, state of physical system)Details
        Append (INSERT)Append to the table.
        First, a temporary table is created and data is populated into it, then an INSERT is performed from the temporary table to the Data Destination table.
        Therefore, half-finished data will not remain in the Data Destination table when a transfer fails in midstream.
        If the Data Destination table does not exist, it is automatically created.
        Postscript (INSERT DIRECT)Append to the table.
        Data is submitted directly to the Data Destination table without creating temporary tables, etc.
        Therefore, data may remain in a half-finished state when a transfer fails midway.
        If the Data Destination table does not exist, it is automatically created.
        TRUNCATE INSERTThe table will be washed.
        First, a temporary table is created and data is populated into it, then an INSERT is performed from the temporary table to the Data Destination table.
        Note that the truncate is performed immediately before the INSERT, so it is a wash.
        Data Destination table index information is maintained.
        All cases washed (REPLACE)The table will be washed.
        First, a temporary table is created and data is submitted to it, and if this is successful, the Data Destination table is deleted and the temporary table is renamed.
        Data Destination table index information, etc. will be lost.
        UPSERT (MERGE)UPSERT the table.
        First, a temporary table is created and all data is populated into it.
        Next, for the Data Destination table, update the temporary table with records for which merge key values exist, and then insert records for which merge key values do not exist.

        Note that if you select UPSERT (MERGE), you can enter a merge key.
        The merge key must be a column with no duplicate values and no null values.
        Was this article helpful?
        What's Next