Skip to content

Commit 33a2b6b

Browse files
mention column addition only after update happens
1 parent 9b38a66 commit 33a2b6b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/integrations/data-ingestion/clickpipes/postgres/schema-changes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ ClickPipes for Postgres can detect schema changes in the source tables and, in s
1010

1111
| Schema Change Type | Behaviour |
1212
| ----------------------------------------------------------------------------------- | ------------------------------------- |
13-
| 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 |
14-
| 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 |
13+
| 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 |
14+
| 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 |
1515
| 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 |

0 commit comments

Comments
 (0)