Google Cloud PostgreSQL
On This Page
Starting Release 2.19, Hevo has stopped supporting XMIN as a query mode for all variants of the PostgreSQL Source. As a result, you will not be able to create new Pipelines using this query mode. This change does not affect existing Pipelines. However, you will not be able to change the query mode to XMIN for any objects currently ingesting data using other query modes.
Google Cloud PostgreSQL is a fully-managed database service that helps you set up, maintain, manage, and administer your PostgreSQL relational databases on the Google Cloud platform.
You can ingest data from your Google Cloud PostgreSQL database using Hevo Pipelines and replicate it to a Destination of your choice.
If you add a column with a default value to a table in PostgreSQL, entries with it are created in the WAL only for the rows that are added or updated after the column is added. As a result, in the case of log-based Pipelines, Hevo cannot capture the column value for the unchanged rows. To capture those values, you need to:
Restart the historical load for the respective object.
Run a query in the Destination to add the column and its value to all rows.
Google Cloud PostgreSQL does not support logical replication on read replicas. To enable log-based replication, you must select the master database instance.
When you delete a row in the Source table, its XMIN value is deleted as well. As a result, for Pipelines created with the XMIN ingestion mode, Hevo cannot track deletes in the Source object(s). To capture deletes, you need to restart the historical load for the respective object.
XMIN is a system-generated column in PostgreSQL, and it cannot be indexed. Hence, to identify the updated rows in Pipelines created with the XMIN ingestion mode, Hevo scans the entire table. This action may lead to slower data ingestion and increased processing overheads on your PostgreSQL database host. Due to this, Hevo recommends that you create the Pipeline in the Logical Replication mode.
Note: The XMIN limitations specified above are applicable only to Pipelines created using the XMIN ingestion mode, which is currently available for Early Access.
The data type Array in the Source is automatically mapped to Varchar at the Destination. No other mapping is currently supported.
If your Source data has indexes (indices) and constraints, you must recreate them in your Destination table, as Hevo does not replicate them from the Source. It only creates the existing primary keys.
Hevo does not set the
__hevo_marked_deletedfield to True for data deleted from the Source table using the TRUNCATE command. This could result in a data mismatch between the Source and Destination tables.
Refer to the following table for the list of key updates made to this page:
|Description of Change
|Updated sections, Specify Google Cloud PostgreSQL Connection Settings and Object and Query Mode Settings to add information about the XMIN ingestion mode.
|Updated section, Object and Query Mode Settings to add a note about the enhanced object selection flow available for log-based Pipelines.
|- Updated section, Source Considerations to add information about limitations of XMIN query mode.
- Removed mentions of XMIN as a query mode.
|Renamed section, Object Settings to Object and Query Mode Settings.
- Set up Log-based Incremental Replication and Whitelist Hevo’s IP Addresses to reflect the changed Google Cloud SQL UI,
- Specify Google Cloud PostgreSQL Connection Settings to describe the schema name displayed in Table and Custom SQL ingestion modes,
- Source Considerations to add information about logical replication not supported on read replicas, and
- Limitations to add limitations about data replicated by Hevo.
|Updated section, Limitations to add information about Hevo not supporting data replication from certain tables.
|Added section, Source Considerations.
|Updated section, Specify Google Cloud PostgreSQL Connection Settings to add a note to inform users that all loaded Events are billable for Custom SQL mode-based Pipelines.
|Updated section, Specify Google Cloud PostgreSQL Connection Settings to mention about SEE MORE in the Select an Ingestion Mode section.
|Updated section, Specify Google Cloud PostgreSQL Connection Settings to add information that you must specify all fields to create a Pipeline.
|Updated section, Specify Google Cloud PostgreSQL Connection Settings to mention about including skipped objects post-Pipeline creation.
|Updated section, Specify Google Cloud PostgreSQL Connection Settings to mention about the connectivity checker.
|- Added sections, Specify Google Cloud PostgreSQL Connection Settings and Object Settings.
|Updated the section, Prerequisites with a note about the logical replication.
|Removed from Limitations that Hevo does not support UUID datatype as primary key.
|Updated section, Set up Log-based Incremental Replication.
|- Updated the section, Limitations to include information about columns with the UUID data type not being supported as a primary key.
- Added WAL replication mode in the Prerequisites section.
- Replaced the section Grant Privileges to the User with Create a Replication User and Grant Privileges.
|Updated the Grant Privileges to the User section to include latest commands.