From 8c6a4fb1a1db11ed8157e07d3ffc79a08144d317 Mon Sep 17 00:00:00 2001 From: Charity Holt <38872070+charholt@users.noreply.github.com> Date: Tue, 25 Mar 2025 13:52:38 -0400 Subject: [PATCH 1/2] Adding clarity on permissions when using the same user from destination --- .../reverse-etl-source-setup-guides/postgres-setup.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md index 04695300ea..e3f71495cf 100644 --- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md +++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md @@ -40,4 +40,10 @@ To set up Postgres with Reverse ETL: * Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results. -After you've successfully added your Postgres source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. \ No newline at end of file +After you've successfully added your Postgres source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. + +### Using the Same User for a Postgres Destination and Reverse ETL? +If you’re using the same database user for both a Segment Postgres warehouse destination (where Segment writes data into Postgres) and Reverse ETL (where Segment reads from Postgres), make sure the user has: +- SELECT or READ access on all source tables for Reverse ETL +- CREATE SCHEMA `__SEGMENT_REVERSE_ETL` permission (or ability to use an existing schema) +- INSERT, UPDATE, and DELETE permissions on tables within `__SEGMENT_REVERSE_ETL` From 38f804cccdda3687e3f5ad762e6af1c0531754f1 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 27 Mar 2025 12:19:59 -0400 Subject: [PATCH 2/2] Apply suggestions from code review --- .../reverse-etl-source-setup-guides/postgres-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md index e3f71495cf..42fe99565d 100644 --- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md +++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md @@ -42,8 +42,8 @@ To set up Postgres with Reverse ETL: After you've successfully added your Postgres source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. -### Using the Same User for a Postgres Destination and Reverse ETL? -If you’re using the same database user for both a Segment Postgres warehouse destination (where Segment writes data into Postgres) and Reverse ETL (where Segment reads from Postgres), make sure the user has: +### How to use the same user for a Postgres destination and Reverse ETL source +If you’re using the same database user for both a Segment [Postgres warehouse destination](/docs/connections/storage/catalog/postgres/) (where Segment writes data into Postgres) and Reverse ETL source (where Segment reads data from Postgres), make sure the user has: - SELECT or READ access on all source tables for Reverse ETL - CREATE SCHEMA `__SEGMENT_REVERSE_ETL` permission (or ability to use an existing schema) - INSERT, UPDATE, and DELETE permissions on tables within `__SEGMENT_REVERSE_ETL`