Skip to content

Adding clarity on permissions when using the same user from destination #7521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 27, 2025
Merged

Adding clarity on permissions when using the same user from destination #7521

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c6a4fb
Adding clarity on permissions when using the same user from destination
charholt Mar 25, 2025
38f804c
Apply suggestions from code review
forstisabella Mar 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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`