Learn more about PostgreSQL Export Integration.

The Data Connector for PostgreSQL enables you to directly import data from your PostgreSQL to Treasure Data.

For sample workflows showing how to import data from your PostgreSQL, view Treasure Boxes.

Continue to the following topics:


  • Basic knowledge of Treasure Data

  • Basic knowledge of PostgreSQL

  • A PostgreSQL instance running remotely, for example on RDS.

Using TD Console

Create a New Connection

When you configure a data connection, you provide authentication to access the integration. In Treasure Data, you configure the authentication and then specify the source information.

  1. Open TD Console.

  2. Navigate to Integrations HubCatalog

  3. Search for and select PostgreSQL. Select Create.

  4. The following dialog opens.

  5. Enter the required credentials and set the parameters. Select Continue.


The host information of the source database, such as an IP address.


The connection port on the source instance. The PostgreSQL default is 5432.


Username to connect to the source database.


The password to connect to the source database.


Check this box to connect using SSL

Specify SSL version

Select which SSL version to use for the connection.

Socket connection timeout

Timeout (in seconds) for socket connection (default is 300).

Network timeout

Timeout (in seconds) for network socket operations. 0 means no timeout.

Name the Connection

  1. Type a name for your connection. If you would like to share this connection with other users in your organization, select Share with others. If this box is unchecked, then the connection is visible only to you.

  2. Select Done.

Transfer Your PostgreSQL Account Data to Treasure Data

After creating the authenticated connection, you are automatically taken to Authentications.

  1. Search for the connection you created. 

  2. Select New Source. The Create Source dialog opens.


  1. Type a name for your Source in the Data Transfer field.

  2. Click Next

Source Table

  1. Edit the following parameters



Database name

The name of the database you are transferring data from. For example, your_database_name.

Use custom SELECT query?

Use if you need more than a simple SELECT (columns) FROM table WHERE (condition).

SELECT columns

If there are only specific columns you would like to pull data from, list them here. Otherwise, all columns are transferred.


The table from which you want to import the data.

WHERE condition

If you need additional specificity on the data retrieved from the table you can specify it here as part of WHERE clause.


Specify if you need the records ordered by a particular field.

 Data Settings

  1. Select Next. The Data Settings page opens.

  2. Optionally, edit the data settings or skip this page of the dialog.




When you want to repeatedly run this transfer, select this checkbox to import data only since the last time the import was run.

Rows per batch

Extremely large datasets can lead to memory issues and subsequently failed jobs. Use this flag to breakdown the import job into batches by the number of rows to reduce the chances of memory issues and failed jobs.

Default timezone

The timezone to be used when doing the import.


This SQL is executed after the SELECT query in the same transaction.

Column Options

Select this option to modify the type of column before importing it. Select Save to save any data setting you have entered.

Default Column Options

Select this option to define the data type according to default SQL types before importing it. Select Save to save any data settings you have entered.

This option is not available in the TD Console. Set this option using TD CLI or TD Workflow


You can see a preview of your data before running the import by selecting Generate Preview.

Data shown in the data preview is approximated from your source. It is not the actual data that is imported.

  1. Click Next.
    Data preview is optional and you can safely skip to the next page of the dialog if you want.

  2. To preview your data, select Generate Preview. Optionally, click Next

  3. Verify that the data looks approximately like you expect it to.

  4. Select Next.

Data Placement

For data placement, select the target database and table where you want your data placed and indicate how often the import should run.

  1.  Select Next. Under Storage you will create a new or select an existing database and create a new or select an existing table for where you want to place the imported data.

  2. Select a Database > Select an existing or Create New Database.

  3. Optionally, type a database name.

  4. Select a Table> Select an existing or Create New Table.

  5. Optionally, type a table name.

  6. Choose the method for importing the data.

    • Append (default)-Data import results are appended to the table.
      If the table does not exist, it will be created.

    • Always Replace-Replaces the entire content of an existing table with the result output of the query. If the table does not exist, a new table is created. 

    • Replace on New Data-Only replace the entire content of an existing table with the result output when there is new data.

  7. Select the Timestamp-based Partition Key column.
    If you want to set a different partition key seed than the default key, you can specify the long or timestamp column as the partitioning time. As a default time column, it uses upload_time with the add_time filter.

  8. Select the Timezone for your data storage.

  9. Under Schedule, you can choose when and how often you want to run this query.

    • Run once:
      1. Select Off.

      2. Select Scheduling Timezone.

      3. Select Create & Run Now.

    • Repeat the query:

      1. Select On.

      2. Select the Schedule. The UI provides these four options: @hourly, @daily and @monthly or custom cron.

      3. You can also select Delay Transfer and add a delay of execution time.

      4. Select Scheduling Timezone.

      5. Select Create & Run Now.

 After your transfer has run, you can see the results of your transfer in Data Workbench > Databases.

Further Information

  • No labels