website logo
⌘K
Getting Started 🚀
What is DataLakeHouse.io?
Our Business-Value Focus
Learn the Basic Concepts
Connectors
Operations Applications
Asana
Aloha POS
Baremetrics
Beans Route
BILL
Bloom Growth
Bullhorn
Calendly
Ceridian Dayforce
ClinicalTrials.gov
ConnectWise
DBT Cloud
DBT Cloud Log Stream
Facebook Ads
Food Delivery Service Connector
Google Analytics 4
Google Play
Harvest
Hubspot
Jira
MailChimp
McLeod Transportation
Microsoft Teams
NetSuite (Oracle NetSuite)
NetSuite SuiteAnalytics
Optimum HRIS
QuickBooks Online
Salesforce
Salesloft
Shift4 Payments
Shopify
Square
Square Marketplace
Stripe
Toast
TriNet
Verizon Wireless Business
Workday HCM
Xero
Zendesk Sell
Zoom
Databases
Files & Object Storage
SQL Data Query
SSH Tunnel Setup for Hosted Database Systems
SQL Playground Editor
SQL Transformations
DBT Cloud Transformations
Terraform: Reverse Terraforming
Sync Bridge (Data Pipelines)
Create a Sync Bridge
Manually Run a Sync Bridge
Deleting a Sync Bridge
Historical Re-sync
Analytics
Access Analytics
Snowflake Usage Analytics
Data Catalog
Create the Catalog
Populate the Catalog
Access the Catalog
Data Warehouse Clouds
❄️Snowflake
Open Source DW Models
Alerts & Notifications
Slack Notifications
Logs & Monitoring
Security
Callback Links
Service Level Agreement (SLA)
Release Notes
July 2023
June 2023
May 2023
April 2023
Q3 2022
Q4 2022
Community Overview
Contributor Agreements
Code Contribution Guide
About
Customer Support
License
Viewpoint
Credit Consumption Breakdown
Docs powered by
Archbee
website logo
Connectors
...
PostgreSQL
FAQ : PostgreSQL

How to Fix XMIN Issues

2min

When no logical replication slot is enabled/existing, XMIN is the default to allow change data capture incremental update concepts to work out of the box.

If you encounter an issue with XMIN replication this is most likely ue to PostgreSQL's internal vacuuming process where too much time has lapsed since the last successful synchronization of data. We see this most often when the autovacuum_freeze_max_age is set to a low value or and/or the Sync Bridge frequency is not set high enough for the amount of data transactions on the source database.

Resolution:

If this is the case for your Sync Bridge data source or you receive an alert regarding this, we recommend the one or all of the options below:

  1. Increase the autovacuum_freeze_max_age value on the PostgreSQL database server
  2. Run the vacuum freeze command on the database server
    1. FYI, the XMIN process in the PostgreSQL database server tracks each transaction in a table with a unique id number, and technically when it reaches the value of the autovacuum_freeze_max_age (the default value is 200M transactions), the server will mark/classify those existing records XMIN id as old records. By running explicitly vacuum freeze it basically allows the process to start over for transactions count.
  3. Switch to a Logical Replication Setup instead of XMIN for how change tracking of incremental changes is handled



Updated 23 May 2023
Did this page help you?
PREVIOUS
FAQ : PostgreSQL
NEXT
How to Fix Replication Slot Performance or Errors?
Docs powered by
Archbee
TABLE OF CONTENTS
Resolution:
Docs powered by
Archbee