@kapa.ai, for xmin type of replication in postgres do we need to enable replication of RDS as well ?

Xmin Replication and RDS No, you do not need to enable logical replication on your PostgreSQL instance (including RDS) when using the xmin replication method. The xmin method works by using PostgreSQL's built-in

xmin

system column (available in all Postgres databases) to track row changes. It does not rely on the Write-Ahead Log (WAL) or logical replication slots — those are only required for CDC (Change Data Capture) replication. [Postgres Troubleshooting] The additional setup steps required for CDC (such as enabling

cloudsql.logical_decoding

or

rds.logical_replication

, granting

REPLICATION

permissions, and creating a replication slot) are not needed for xmin. [Cloud SQL Postgres] For xmin, you only need to: 1. Create a dedicated read-only Postgres user with

SELECT

permissions on the relevant schemas/tables. 2. Select Standard (xmin) as the replication method in the Airbyte UI. However, do keep in mind the limitations of xmin replication: [Postgres Troubleshooting] • It cannot capture row deletions. • It requires a full table scan, which can be slow on large tables. • It is susceptible to transaction ID (XID) wraparound issues. • For very large databases (> 500 GB), CDC is recommended instead. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, why i can't see no stream do i need to add them in publication ?

Streams Not Visible in Airbyte Since you're using xmin replication (not CDC), you do not need to add tables to a publication — publications are only required for CDC mode. If you can't see any streams, here are the most likely causes based on the knowledge sources: 1. User Permissions Ensure your Postgres user has been granted the correct permissions on the schema and tables:

GRANT USAGE ON SCHEMA <schema_name> TO <user_name>;
GRANT SELECT ON ALL TABLES IN SCHEMA <schema_name> TO <user_name>;
ALTER DEFAULT PRIVILEGES IN SCHEMA <schema_name> GRANT SELECT ON TABLES TO <user_name>;

[Cloud SQL Postgres] 2. Schema Not Listed in Source Config When setting up the Postgres source in Airbyte, make sure you have explicitly listed the schemas you want to sync. These are case-sensitive, and only

public

is selected by default. If your tables are in a different schema, you need to add it. [Cloud SQL Postgres] 3. Known Bug with Older Connector Versions There was a known issue where Postgres source versions after

0.4.10

failed to discover tables. This was fixed in version

0.4.14

. If you're on an older connector version, upgrading should resolve it. [Forum: Failure to discover streams] 4. Nullable Columns Issue Another known bug in connector version

1.0.10

caused some tables to not show incremental options or not appear correctly. Upgrading to

1.0.11

or later resolved this. [Forum: No incremental option] Recommended action: Check your schema permissions, verify the schema name is correctly entered in the source config, and ensure you're on an up-to-date connector version. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

my schema name is GOLD how to put in source

Adding a Custom Schema Name in Postgres Source Since your schema name is

GOLD

, you need to be careful because schema names are case-sensitive in Airbyte's Postgres source configuration. When setting up your Postgres source in the Airbyte UI: 1. Click Sources → select your Postgres source 2. In the Schemas field, enter

GOLD

(in uppercase, exactly as it appears in your database) > By default, only

public

is listed. You need to replace or add your schema name here. [Cloud SQL Postgres] If you're using a YAML configuration (e.g., via Octavia CLI), it would look like this:

configuration:
  schemas: ["GOLD"]

[Version Control Configs] Also make sure your Postgres user has the correct permissions on the

GOLD

schema:

GRANT USAGE ON SCHEMA "GOLD" TO <user_name>;
GRANT SELECT ON ALL TABLES IN SCHEMA "GOLD" TO <user_name>;
ALTER DEFAULT PRIVILEGES IN SCHEMA "GOLD" GRANT SELECT ON TABLES TO <user_name>;

> Note the use of double quotes around

GOLD

in the SQL commands — this preserves the uppercase casing in PostgreSQL. Without quotes, PostgreSQL would fold it to lowercase. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.