Skip to content

Commit 8c6a4fb

Browse files
authored
Adding clarity on permissions when using the same user from destination
1 parent 22a4b2a commit 8c6a4fb

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -40,4 +40,10 @@ To set up Postgres with Reverse ETL:
4040

4141
* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.
4242

43-
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.
43+
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.
44+
45+
### Using the Same User for a Postgres Destination and Reverse ETL?
46+
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:
47+
- SELECT or READ access on all source tables for Reverse ETL
48+
- CREATE SCHEMA `__SEGMENT_REVERSE_ETL` permission (or ability to use an existing schema)
49+
- INSERT, UPDATE, and DELETE permissions on tables within `__SEGMENT_REVERSE_ETL`

0 commit comments

Comments
 (0)