Changing replica identity to full for Postgres integration

Summary

The user is inquiring about changing the replica identity to full for the Postgres integration based on the information provided in the Airbyte documentation.


Question

Yes, docs https://docs.airbyte.com/integrations/sources/postgres|here say you need to change the replica identity to full.

> In rare cases, if your tables use data types that support https://www.postgresql.org/docs/current/storage-toast.html|TOAST or have very large field values, consider instead using replica identity type full: ALTER TABLE tbl1 REPLICA IDENTITY FULL;. Ensure that TOAST-able tables use non-TOAST-able primary keys (integers, varchars, etc), and there will only be a <https://xata.io/blog/replica-identity-full-performance|modest increase in resource utilization, in addition to increased WAL storage size>.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["change-replica-identity", "postgres-integration", "airbyte-documentation"]