From 33a2b6b0999a3742981353d1baeeabca009fbc39 Mon Sep 17 00:00:00 2001 From: Amogh-Bharadwaj Date: Mon, 15 Sep 2025 15:58:53 +0530 Subject: [PATCH 1/3] mention column addition only after update happens --- .../data-ingestion/clickpipes/postgres/schema-changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md b/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md index 96903ac3e45..d916564cdca 100644 --- a/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md +++ b/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md @@ -10,6 +10,6 @@ ClickPipes for Postgres can detect schema changes in the source tables and, in s | Schema Change Type | Behaviour | | ----------------------------------------------------------------------------------- | ------------------------------------- | -| Adding a new column (`ALTER TABLE ADD COLUMN ...`) | Propagated automatically. The new column(s) will be populated for all rows replicated after the schema change | -| Adding a new column with a default value (`ALTER TABLE ADD COLUMN ... DEFAULT ...`) | Propagated automatically. The new column(s) will be populated for all rows replicated after the schema change, but existing rows will not show the default value without a full table refresh | +| Adding a new column (`ALTER TABLE ADD COLUMN ...`) | Propagated automatically once the table gets an insert/update/delete. The new column(s) will be populated for all rows replicated after the schema change | +| Adding a new column with a default value (`ALTER TABLE ADD COLUMN ... DEFAULT ...`) | Propagated automatically once the table gets an insert/update/delete. The new column(s) will be populated for all rows replicated after the schema change, but existing rows will not show the default value without a full table refresh | | Dropping an existing column (`ALTER TABLE DROP COLUMN ...`) | Detected, but **not** propagated. The dropped column(s) will be populated with `NULL` for all rows replicated after the schema change | From 525ab5842efd6e1bf29b6e111a72fd6b3267bb94 Mon Sep 17 00:00:00 2001 From: Amogh-Bharadwaj Date: Mon, 15 Sep 2025 15:59:16 +0530 Subject: [PATCH 2/3] fix typo --- docs/integrations/data-ingestion/clickpipes/postgres/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/data-ingestion/clickpipes/postgres/faq.md b/docs/integrations/data-ingestion/clickpipes/postgres/faq.md index 8ad5478fe18..310c8ad0fff 100644 --- a/docs/integrations/data-ingestion/clickpipes/postgres/faq.md +++ b/docs/integrations/data-ingestion/clickpipes/postgres/faq.md @@ -32,7 +32,7 @@ To set the replica identity to FULL, you can use the following SQL command: ```sql ALTER TABLE your_table_name REPLICA IDENTITY FULL; ``` -REPLICA IDENTITY FULL also enabled replication of unchanged TOAST columns. More on that [here](./toast). +REPLICA IDENTITY FULL also enables replication of unchanged TOAST columns. More on that [here](./toast). Note that using `REPLICA IDENTITY FULL` can have performance implications and also faster WAL growth, especially for tables without a primary key and with frequent updates or deletes, as it requires more data to be logged for each change. If you have any doubts or need assistance with setting up primary keys or replica identities for your tables, please reach out to our support team for guidance. From cb2ddc332a15b1ae67f60ec5ce3668d94f0a609d Mon Sep 17 00:00:00 2001 From: Amogh-Bharadwaj Date: Mon, 15 Sep 2025 16:04:34 +0530 Subject: [PATCH 3/3] add line on controlling syncs --- .../data-ingestion/clickpipes/postgres/schema-changes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md b/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md index d916564cdca..3033daad14f 100644 --- a/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md +++ b/docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md @@ -13,3 +13,5 @@ ClickPipes for Postgres can detect schema changes in the source tables and, in s | Adding a new column (`ALTER TABLE ADD COLUMN ...`) | Propagated automatically once the table gets an insert/update/delete. The new column(s) will be populated for all rows replicated after the schema change | | Adding a new column with a default value (`ALTER TABLE ADD COLUMN ... DEFAULT ...`) | Propagated automatically once the table gets an insert/update/delete. The new column(s) will be populated for all rows replicated after the schema change, but existing rows will not show the default value without a full table refresh | | Dropping an existing column (`ALTER TABLE DROP COLUMN ...`) | Detected, but **not** propagated. The dropped column(s) will be populated with `NULL` for all rows replicated after the schema change | + +Note that column addition will be propagated at the end of a batch's sync, which could occur after the sync interval or pull batch size is reached. More information on controlling syncs [here](./controlling_sync.md) \ No newline at end of file