PolarDB PostgreSQL Instruction

  • Last update: April 09, 2025
  • iconNote:
    This document provides a detailed instruction for using a PolarDB PostgreSQL database in FineDataLink, including its usage limitations and special settings varying with function modules, helping you better understand and apply the data source.

    Data Development - Scheduled Task

    The DDL synchronization function of Scheduled Task does not apply to PolarDB PostgreSQL databases.

    Data Source

    You can read partition tables from the PolarDB PostgreSQL database in scheduled tasks, as shown in the following figure.

    For details, see Partition Table Creation and Data Reading/Writing.

    1.png

    Data Destination and Mapping

    You can select partition tables as data destinations in scheduled tasks, as shown in the following figure.

    2.png

    You can set partition keys when Target Table is set to Auto Created Tables in scheduled tasks, as shown in the following figure.

    For details, see Partition Table Creation and Data Reading/Writing.

    3.png

    Details about the configuration method are as follows:

    1. PolarDB PostgreSQL 14 supports three partitioning methods: RANGEHASH, and LIST. PolarDB Oracle 2.0 supports two partitioning methods: RANGE and LIST.

    2. RANGE and LIST allow you to select multiple fields as partition fields.

    3. RANGE allows you to set multiple partition keys and set the default partition.

    4. RANGE and LIST allow you to leave Partition Name empty, in which case a default name will be automatically generated based on the partition position.

    5. Explicit partition definitions are required when you create a partitioned table in PolarDB Oracle 2.0. If the source table is a foreign table and unique indexes are created on the target table, you cannot attach the source table as a partition of the target table.

    6. PolarDB PostgreSQL 14 allows you to use any column as a primary key or foreign key in a partition table.

    7. For interval range partitioning, you cannot specify NULL, Not-a-Number, or Infinity values in a partition key column.

    Data Pipeline

    For details, see Overview of Data Pipeline.

    1. You can set partition keys when Target Table is set to Auto Created Table in pipeline tasks, as shown in the following figure.

    4.png

    2. Synchronize Source Table Structure Change is supported when the PolarDB PostgreSQL database serves as the target end.

    3. Synchronization Without Primary Key is not supported when the PolarDB PostgreSQL database serves as the target end.

    Data Service

    For details, see Overview of Data Service.

    Data Service allows you to select a partition table as the data source, as shown in the following figure.

    5.png

    Data Management

    This database supports the Database Table Management function but does not support the Lineage Analysis function.


    附件列表


    主题: Data Source Configuration
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy