--- title: "PostgreSQL" slug: "postgresql-overview-replicate-cloud" updated: 2026-10-30T11:57:42Z published: 2026-10-30T11:57:42Z canonical: "skthelp.syniti.com/postgresql-overview-replicate-cloud" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # PostgreSQL ## Overview Replicate Preview supports structured data replication between PostgreSQL and other supported systems, allowing it to operate as both a source and target endpoint. By configuring connections and selecting required datasets, users can establish replication pipelines that ensure controlled and consistent data delivery. The platform manages execution and resource handling, simplifying deployment across PostgreSQL environments. > [!NOTE] > Note > > PostgreSQL is currently supported as both a **source and target endpoint** in Replicate Preview, limited to **Snapshot (full load) replication mode**, with Change Data Capture (CDC) and streaming replication not yet supported. ### Supported Versions PostgreSQL **versions 15 and later** are supported. ## User Permissions ### Using PostgreSQL as source connection The following are the user permissions required using PostgreSQL as source in Snapshot mode: - Authority to connect a database - Authority to select tables ```plaintext CREATE USER WITH PASSWORD 'your_password'; GRANT CONNECT ON DATABASE your_database TO ; GRANT SELECT ON ALL TABLES IN SCHEMA TO ; ``` ### Using PostgreSQL as target connection The user performing operations should have the following PostgreSQL permissions: - **CONNECT:** Required to connect to the database. - **USAGE on Schemas:** Grants access to specific schemas where tables are located. - **SELECT on Tables:** Only used when tables already exist on the target catalog. - **INSERT/UPDATE/DELETE:** If changes to data or loading back are needed, these privileges are also required on the target tables. ```plaintext CREATE USER your_user WITH PASSWORD 'your_password'; GRANT CONNECT ON DATABASE your_database TO your_user; GRANT USAGE ON SCHEMA your_schema TO your_user; GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA your_schema TO you_user; ``` #### Table casing behavior change Starting November 1, 2026, Replicate Preview will create PostgreSQL target tables using the same letter casing as the source object name. Previously, PostgreSQL target table names were automatically converted to lowercase. As part of Replicate Preview's internal query processing, source object casing is now preserved when target tables are created. For example, | **Source table name** | **PostgreSQL target table created** | | --- | --- | | Customer | Customer | | CUSTOMER | CUSTOMER | | customer | customer | **Recommendation** Before creating new PostgreSQL replications, verify that downstream consumers (views, ETL processes, reporting tools, and custom SQL) can handle case-sensitive object names. If required, update SQL statements to reference object names using the exact casing and double quotes, for example: `SELECT * FROM "Customer";` Alternatively, adjust downstream objects and naming conventions to align with the preserved source casing. > [!NOTE] > Note > > This change affects newly created replications and aligns PostgreSQL target object naming with the source system object names by preserving their original casing. ## **Connection Considerations** If you do not have a connection configured, refer to [Connecting to PostgreSQL](/v1/docs/connecting-to-postgresql) for step-by-step instructions: When configuring and using a connection to PostgreSQL, consider the following: | Configuration | Details | | --- | --- | | Connection Parameters | Ensure that all required connection properties are correctly defined, including hostname, port (default: 5432), database name, username, and password. Incorrect values are a common cause of connection failures. | | Schema Access and Search Path | Ensure that the user has access to the required schemas and that the correct schema is referenced. PostgreSQL environments with multiple schemas may require explicit schema qualification to avoid object resolution issues. | | Network Connectivity and Access Control | Confirm that the PostgreSQL server is accessible from the service. Verify firewall rules, security groups, or cloud network configurations (for example, AWS Security Groups or Azure NSGs) allow inbound connections. | | SSL/TLS Configuration | If SSL is required, ensure that the PostgreSQL server is configured to accept secure connections and that the appropriate SSL mode is selected in the connection settings. | | Naming Conventions and Case Sensitivity | Databases, schemas, and tables should follow lowercase naming conventions to avoid inconsistencies. If objects were created using quoted identifiers with uppercase or mixed case, exact casing must be used during replication, otherwise object resolution errors may occur. | | Data Type Compatibility | Review data type mappings between PostgreSQL and the target system. Pay attention to types such as `NUMERIC`, `TIMESTAMP`, and `JSON/JSONB`, which may require validation depending on the target. | | Large Table and Performance Considerations | For large datasets, consider query performance, indexing, and system resource utilization. Scheduling replication during low-usage periods can help reduce impact on the source system. | ## Next Steps In Replicate Preview, configure your workspace using this system datastore and start replicating data. Refer to [Configure Workspace: Datastores](/v1/docs/configure-workspace-datastores) for more information. ## Related Articles - [Create a Connection](/v1/docs/create-a-connection) - [Configure Workspace: Datastores](/v1/docs/configure-workspace-datastores) - [Connecting to PostgreSQL](/v1/docs/connecting-to-postgresql)